Tobias Ribizel

Sorry for the misleading wording - Ginkgo 2.0 is a future release where we need to make a few interface breaks to fix architectural issues that we can't address with...

I wish there was a better library for YAML parsing, but I guess this will have to do. There are some issues with how yaml-cpp handles assignment and copies https://github.com/jbeder/yaml-cpp/issues/1275....

I can reproduce this behavior, but I am willing to say that this is not UB - this is a `static_cast` from a derived class to a base class for...

It definitely depends on the order of base classes, but in our case, it would fail very loudly because it will lead to an uninitialized `shared_ptr` for the executor, so...

Can confirm this issue, we don't test nvhpc with MPI, so it doesn't come up in our pipelines

Seems slightly broken ``` ==> [2025-05-29-12:42:02.173968] Error: AttributeError: 'function' object has no attribute 'expanded' The 'llvm' package cannot find an attribute while trying to build from sources. You can fix...

Doesn't seem to work: ``` > spack -e stack find ==> In environment stack ==> 160 root specs [+] [email protected] [+] [email protected] [+] [email protected] [+] [email protected] [+] [email protected] [+] [email protected]...

Here is the same thing with debug output [spack-error-output.txt](https://github.com/user-attachments/files/20644066/spack-error-output.txt)

Here is a "small" reproducer: [spack.yaml.txt](https://github.com/user-attachments/files/20709174/spack.yaml.txt) [spack.lock.txt](https://github.com/user-attachments/files/20709177/spack.lock.txt) This just contains `llvm@7` and `llvm@13` with a (somewhat) shared environment, but any concretization thereof should work, as the versions use the same...

Seems to work, many thanks! I was able to build 7 LLVM versions in parallel without a failure