-
Notifications
You must be signed in to change notification settings - Fork 767
{numlib}[intel/2025b] GDAL v3.11.3, Armadillo v15.0.1, arpack-ng v3.9.1 #24641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
{numlib}[intel/2025b] GDAL v3.11.3, Armadillo v15.0.1, arpack-ng v3.9.1 #24641
Conversation
…l-2025b.eb, arpack-ng-3.9.1-intel-2025b.eb
|
@boegelbot please test @ jsc-zen3 |
|
@pavelToman: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 3557832245 processed Message to humans: this is just bookkeeping information for me, |
Updated software
|
|
Test report by @boegelbot |
|
Test report by @pavelToman |
|
Test report by @pavelToman |
|
Test report by @pavelToman |
Micket
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
|
Test report by @Micket |
|
I'm getting a hard compiler crash on GDAL here |
|
I'm seeing the same problem as @Micket ... Test report coming up @pavelToman Any ideas? |
|
Test report by @boegel |
|
Looks quite similar to llvm/llvm-project#46778, but that bug was fixed in LLVM in 2020... |
|
@boegelbot please test @ jsc-zen3 |
|
@boegel: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 3584812250 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
Test report by @pavelToman |
@boegel I think I find something: With your failing compilation on shinx the flags are: I think the Another fix could be the lowering of optimalization for Also @Micket's flags are different: I think that failing compilation is because of |
|
Test report by @pavelToman Test with |
|
Test report by @pavelToman Test WITHOUT |
|
Test report by @pavelToman Test WITHOUT Seems on the accelgor it works even with default flag |
|
I update the toolchainopts, @Micket could you test it again on |
|
@boegelbot please test @ jsc-zen3 |
|
Test report by @pavelToman Test with |
|
@pavelToman: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 3589329641 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @jfgrimm |
|
The failure is awfully similar to the failure we saw with GSL. Here, the solution was to remove easybuild-easyconfigs/easybuild/easyconfigs/g/GSL/GSL-2.8-intel-compilers-2025.2.0.eb Line 22 in 38c7d80
I reported this to Intel via support ticket ID 06662244 back in August. For GSL, they came up with a solution, where a specific loop needs a This only fails on systems with AVX-512 as far as I understand. |
|
Test report by @pavelToman Test with |
|
Test report by @boegelbot |
| data translation and processing.""" | ||
|
|
||
| toolchain = {'name': 'intel', 'version': '2025b'} | ||
| toolchainopts = {'usempi': True, 'pic': True, 'optarch': '-march=x86-64-v3'} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hardcoding -march=x86-64-v3 here is not a good idea.
Maybe try using this instead:
| toolchainopts = {'usempi': True, 'pic': True, 'optarch': '-march=x86-64-v3'} | |
| toolchainopts = {'usempi': True, 'pic': True, 'precise': True} |
That will avoid the use of -fp-speculation=safe, so it's a way of dancing around the problem that @Thyre mentioned
(created using
eb --new-pr)resolves vscentrum/vsc-software-stack#615