chapel
chapel copied to clipboard
chapel-lang
a Productive Parallel Programming Language
PR #25896 avoids array allocation when moving to a different domain with the same index set, but only for DefaultRectangular arrays. That PR uses the approach of adding an optional...
### Summary of Problem **Description:** I tried to build Chapel 2.1 on a system where ROCm 6.0.3 is the default and ROCm 5.4.6 is loaded. The reason for this is...
Currently we error out (saying that `var` intents aren't supported for `foreach`) if you attempt something like this: ``` foreach i in 1..100 with (var x = new MyThing()) {...
I've stumbled into this several times in the past. It could be really frustrating and confusing, but at the same time it could also be related to my setup as...
The runtime doesn't seem to report the correct number of devices in this config. ```chpl for loc in Locales do on loc { writeln(here, " ", here.gpus.size); } ``` reports...
I often find myself doing multiple reductions of the same type in forall loops (eg. multiple accumulators). The way I currently do this is to specify separate reduce intents (as...
### Summary of Problem The compiler fails to resolve a promoted call when the callee is from another `import`ed module. However, when the module is `use`d, it resolves and then...
Fixes #24107 by adding overloads or optional parameters to each of the `ChapelIO.write*` procs to support writing to a `fileWriter` other than `stdout`. This allows user code to call e.g....
Adds support to use Chapel with LLVM 19 Testing: - [x] build with gcc 7.5 on linux64 without CHPL_DEVELOPER - [x] build with gcc 7.5 on linux64 with CHPL_DEVELOPER -...
This was asked in Gitter before, but I can't find the context. Today, I wanted to confirm `gpu.itersPerThread` behavior in the following code: ```chpl on here.gpus[0] { foreach i in...