parsec
parsec copied to clipboard
PaRSEC is a generic framework for architecture aware scheduling and management of micro-tasks on distributed, GPU accelerated, many-core heterogeneous architectures. PaRSEC assigns computation threads...
## Description In a jdf file, you can specify the type of kernel you want by adding [type=ARCH]. If you declare [type=CPU], the generated program will crash with very little...
## Describe the bug Building TTG with GCC 11.4.0 raises a bunch of warnings from PaRSEC: ``` /home/jschuchart/src/ttg/ttg/build/_deps/parsec-src/parsec/class/list.h: In function 'parsec_list_item_t* parsec_list_nolock_pop_back(parsec_list_t*)': /home/jschuchart/src/ttg/ttg/build/_deps/parsec-src/parsec/class/list_item.h:326:16: warning: '--' expression of 'volatile'-qualified type is...
## Describe the bug In PTG, when data is from memory and a `type` keyword is provided, there will be no data movement to GPU, e.g., `READ A
**[Original report](https://bitbucket.org/icldistcomp/parsec/issue/290) by me.** ---------------------------------------- This name does not make sense anymore, we should simplify it to something less weird/internal looking as it is part of the user-facing interface.
## Description In preparation for v4.0, we use dplasma to validate correctness. This issue will track what does and does not work in dplasma. ### Describe the solution you'd like...
Fixes issue #641 * [ ] capture ci tag and compile for Cuda or HIP based on this tag, not on availability of the software stack. * [ ] decide...
## Describe the bug The stress:gpu compiled with CUDA support may crash when run on a system without a CUDA GPU. See https://github.com/ICLDisco/parsec/actions/runs/8190649752/job/22398165838?pr=515 Note that there appears to be some...
## Describe the bug If we pass zero as size to `zone_malloc` it will return `NULL`, which will be interpreted by `kernel_push` as an out-of-memory situation so the task will...
Rework the bindings. The main idea is to inherit the bindings from the batch scheduler, and then work from there.
## Describe the bug Two type of memory leaks cause PaRSEC to segfault sporadically when compiled in Debug mode. The first one gives the following ouput with valgrind ``` ==196556==...