The Wayback Machine - https://web.archive.org/web/20200526145030/https://github.com/topics/gpgpu
Skip to content
#

gpgpu

Here are 299 public repositories matching this topic...

hops
hops commented Mar 28, 2019

This is follow up of #1969 intended as a discussion on how this rule should behave.
It would be great if @jfoug and/or @magnumripper would join so we can battle it out and make it consistent between hashcat and john.

As I mentioned in the original report I assumed that given the input word foobar and the rule ef the mangled output should be FOobar. This is based on my first thought when

futhark
athas
athas commented Jul 24, 2019

Tools such as gofmt are very useful for quickly cleaning reformatting code according to some coding style. I think we need the same for Futhark. It's a bit more complicated to do this for an expression-oriented language than a statement-oriented one, but there is prior art we can look at (like Brittany for Haskell).

While constructing futhark fmt i

MetalPetal
OlyRice
OlyRice commented May 4, 2020

Hi, don't know if I am being stupid but are the values for the filters listed anywhere in documentation or source code?

For example if I want to find the min/max value for the Saturation filter so that I can apply these values to slider where can I find them? Had a look through the Filters folder in the framework but was unable to find any info.

Thanks

Checklist

  • I've read the
tvandera
tvandera commented Dec 21, 2018

Running bench_cg. py from the examples, gives me this error:

python bench_cg.py
ArrayFire v3.6.2 (CUDA, 64-bit Linux, build dc38ef1)
Platform: CUDA Toolkit 10, Driver: 410.79
[0] Tesla K80, 11442 MB, CUDA Compute 3.7
-1- Tesla K80, 11442 MB, CUDA Compute 3.7
-2- Tesla K80, 11442 MB, CUDA Compute 3.7
-3- Tesla K80, 11442 MB, CUDA Compute 3.7

Testing benchmark functions...
Tracebac
DABH
DABH commented Dec 2, 2019

It seems like the parameter names used to control AMG and solver settings are pretty different for the MPI vs. non-MPI versions of the runtime AMGCL interface. For example, in examples/mpi/solve_mm_mpi.cpp, we have

prm.put("local.coarsening.type", coarsening);
prm.put("local.relax.type",      relaxation);
prm.put("isolver.type",          iterative_solver);

but these parameters lik

Improve this page

Add a description, image, and links to the gpgpu topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the gpgpu topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.