The following tarball contains all our unit tests that fail with the nvfortran 23.1 (but do work with ifort, gfortran and nagfor). If you unpack, and do make, then you can check the individual tests with ./whizard_check --check testXX (with XX from 01 to 44) whizard-230404-2235.tar.gz (1.9 MB) {n…

Thanks Juergen, This will take me a bit to get through these to determine the issues and then report them to engineering. The package doesn’t include the reference files so I downloaded Whizard 3.1.2 from https://whizard.hepforge.org/ and used the files from “share/tests/unit_tests/ref-output” So…

Hi Mat, yes, indeed, there are a lot of things that have the same root cause, and some don’t work for you without the setup on my computer. I exchanged the tarball above, which should now contain also the reference files. I will reduce the cases further. I put the next stage of reduction here: whi…

Here is a first separate test case, where the allocation of a polymorphic entity from an abstract base entity leads to a segmentation faul, and a tarball (v3) where I removed that individual test case. test_alloc_polymorph.f90 (4.1 KB)

And because I can only put one link in a post, here comes the reduced reproducer container: whizard-repro_v3.tar.gz (1.1 MB)

I isolated another issue which has to do with allocatable character objects, here: [image] Nvfortran bug(s) with allocatable character objects nvc, nvc++ and nvfortran This is another spin-off from my master post (which I will link in a minute), the following code leads to…

There is another isolated single test from this test suite reported here: [image] Another segmentation fault with compiled nvfortran code nvc, nvc++ and nvfortran This is another test case from the WHIZARD test suite,which segfaults when compiled with nvfortran, but works …

Another spin-off from this is here: [image] Segfault when setting real component of UDDT component of UDDT nvc, nvc++ and nvfortran Hi Nvidia team, this is another problem report from our test suite. A UDDT (particle_set_t) that has a UDDT (particle_t) as component gets a…

Matt, this is now the tarball with 5 or 6 remaining cases, I will stop it for now. If you like, please contunue: whizard_v4.tar.gz (886.9 KB) The tests are labelled test_02/03/04/05/06/10/12/15.

I removed all the separate issues from the tarball, which has shrunk now quite a bit. There are only 5 different tests left, test02-06. The rest were apparently duplicates. whizard_v5.tar.gz (258.6 KB)

Collection of nvfortran problems in our code

Accelerated Computing HPC Compilers nvc, nvc++ and nvfortran

juergen.reuter April 13, 2023, 3:14pm 6

I isolated another issue which has to do with allocatable character objects, here:

Topic		Replies	Views
Nvfortran bug(s) with allocatable character objects nvc, nvc++ and nvfortran nvbugs	2	636	April 13, 2023
Another segmentation fault with compiled nvfortran code nvc, nvc++ and nvfortran nvbugs	2	854	April 20, 2023
Nvfortran leads to wrong code with allocating polymorphic objects nvc, nvc++ and nvfortran nvbugs	2	604	April 11, 2023
Segmentation fault with nvfortran 23.1 nvc, nvc++ and nvfortran nvbugs	2	657	May 10, 2023
Segmentation fault on valid code with nvfortran 23.1 nvc, nvc++ and nvfortran nvbugs	1	687	May 16, 2023
Nvfortran 23.x segmentation fault on valid code nvc, nvc++ and nvfortran	1	559	May 4, 2023
Compiler bug: allocatable polymorphic types with TBPs acting on allocatable array nvc, nvc++ and nvfortran	4	84	March 25, 2026
Valid code leads to allocation memory excess or segmentation violation nvc, nvc++ and nvfortran nvbugs	2	554	May 17, 2023
Segfault connected to procedure pointer in nvfortran nvc, nvc++ and nvfortran	1	464	June 3, 2021
Bug report for nvfortran nvc, nvc++ and nvfortran nvbugs	1	423	November 19, 2020

Collection of nvfortran problems in our code

Related topics