[Bug libfortran/108056] [12/13 Regression] backward compatibility issue between 11 and 12

2022-12-12 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108056 --- Comment #11 from Gilles Gouaillardet --- gfortran-11 compiles and run correctly when it uses libgfortran-11. To be perfectly clear, compilation always work: the issue occurs at runtime when gfortran-11 compiled code uses libgfortran-12).

[Bug libfortran/108056] backward compatibility issue between 11 and 12

2022-12-10 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108056 --- Comment #3 from Gilles Gouaillardet --- For the sake of completeness, debian/ubuntu ships libgfortran.a (read, the static library) from gfortran-11, so I can get this reproducer work if compiling with -static-libgfortran. I also manually

[Bug libfortran/108056] backward compatibility issue between 11 and 12

2022-12-10 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108056 --- Comment #2 from Gilles Gouaillardet --- ubuntu does not ship libgfortran.so from gfortran-11. I tried on a RedHat box, and the issue only occurs when - I compile with gfortran-11 - *and* I force libgfortran-12 (so if i use the same

[Bug libfortran/108056] New: backward compatibility issue between 11 and 12

2022-12-10 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 54062 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54062=edit a simple reproducer The attached program crashes when compi

[Bug c/105449] suspicious optimization since GCC 10.1.0 from -O2

2022-05-01 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105449 --- Comment #4 from Gilles Gouaillardet --- Thanks for the clarification!

[Bug c/105449] suspicious optimization since GCC 10.1.0 from -O2

2022-05-01 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105449 Gilles Gouaillardet changed: What|Removed |Added CC||gilles.gouaillardet at gmail dot

[Bug c/105449] suspicious optimization since GCC 10.1.0 from -

2022-05-01 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105449 --- Comment #1 from Gilles Gouaillardet --- Created attachment 52916 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52916=edit a simple reproducer

[Bug c/105449] New: suspicious optimization since GCC 10.1.0 from -

2022-05-01 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: ---

[Bug target/104152] New: ICE with -Ofast -march=armv8.2-a+sve -msve-vector-bits=scalable

2022-01-20 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 52248 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52248=edit a simple reproducer The attac

[Bug target/104005] [12 Regression] Regression on aarch64+sve with -O2 -fPIC since r12-5204

2022-01-19 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104005 --- Comment #7 from Gilles Gouaillardet --- Thanks Richard for the quick fix! Unfortunately, I just found an other (and much older) issue (ICE, only at -Ofast) I reported at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104112

[Bug target/104112] ICE with -Ofast -march=armv8.2-a+sve -msve-vector-bits=512

2022-01-19 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104112 --- Comment #1 from Gilles Gouaillardet --- Created attachment 52227 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52227=edit a slightly rewritten reproducer that passes compilation

[Bug target/104112] New: ICE with -Ofast -march=armv8.2-a+sve -msve-vector-bits=512

2022-01-19 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 52226 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52226=edit a simple reproducer The attac

[Bug target/104005] [12 Regression] Regression on aarch64+sve with -O2 -fPIC since r12-5204

2022-01-17 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104005 --- Comment #3 from Gilles Gouaillardet --- Created attachment 52210 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52210=edit before/after (preprocessed sources + assembly)

[Bug target/104005] New: Regression on arm+sve with -O2 -fPIC

2022-01-13 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- The GROMACS (2021.3) non regression test suite now hangs with the latest trunk when shared libraries are used from -O2 when two or more thread-MPI are used. I only tried

[Bug target/102252] svbool_t with SVE can generate invalid assembly

2021-09-20 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102252 --- Comment #6 from Gilles Gouaillardet --- I am happy to confirm this issue is fixed in the latest 12-20210919 snapshot :-) FWIW, I was not yet able to build GROMACS because of an other issue that was introduced last week. I reported it at

[Bug target/102421] ICE with -march=armv8.2-a+sve -O3

2021-09-20 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102421 --- Comment #2 from Gilles Gouaillardet --- Created attachment 51487 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51487=edit a trimmed reproducer (FWIW - include files are missing)

[Bug target/102421] ICE with -march=armv8.2-a+sve -O3

2021-09-20 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102421 --- Comment #1 from Gilles Gouaillardet --- Created attachment 51486 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51486=edit a (compressed) pre-processed reproducer

[Bug target/102421] New: ICE with -march=armv8.2-a+sve -O3

2021-09-20 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- This is a new issue that happens with -march=armv8.2-a+sve -O3 with the latest snapshot (12-20210919). FWIW, no crash with - 12-20210912 (last week snapshot) - -march

[Bug target/102252] svbool_t with SVE can generate invalid assembly

2021-09-09 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102252 --- Comment #1 from Gilles Gouaillardet --- Created attachment 51430 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51430=edit a test that works FWIW, the attached test_svfloat.cpp passes. It is very similar to test_svbool.cpp but it

[Bug target/102252] New: svbool_t with SVE can generate invalid assembly

2021-09-09 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
: target Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 51429 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51429=edit a simple reproducer Let's consider the attached test_svbool.

[Bug target/102226] ICE with -O3 -msve-vector-bits=128

2021-09-07 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102226 --- Comment #2 from Gilles Gouaillardet --- Created attachment 51421 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51421=edit preprocessed reproducer Here is the preprocessed reproducer

[Bug target/102226] New: ICE with -O3 -msve-vector-bits=128

2021-09-07 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 51419 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51419=edit A quite simple reproducer The attached reproducer crashes the latest LATEST

[Bug target/101053] Incorrect code at -O1 on arm64

2021-06-14 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101053 --- Comment #9 from Gilles Gouaillardet --- And here is the one-liner to fix this mess --- orig/OpenBLAS-0.3.15/kernel/arm64/dznrm2_thunderx2t99.c 2021-05-03 06:50:22.0 +0900 +++ OpenBLAS-0.3.15/kernel/arm64/dznrm2_thunderx2t99.c

[Bug target/101053] Incorrect code at -O1 on arm64

2021-06-14 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101053 --- Comment #8 from Gilles Gouaillardet --- It seems OpenBLAS is to be blamed after all ... >From kernel/arm64/dznrm2_thunderx2t99.c: #define REGINF "d9" static void nrm2_compute(BLASLONG n, FLOAT *x, BLASLONG inc_x,

[Bug target/101053] Incorrect code at -O1 on arm64

2021-06-14 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101053 --- Comment #7 from Gilles Gouaillardet --- Note you have to 'make clean' before re-running 'make ...' with different options. Otherwise, pretty much nothing gets rebuilt.

[Bug target/101053] Incorrect code at -O1 on arm64

2021-06-14 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101053 --- Comment #6 from Gilles Gouaillardet --- I will set the watchpoint and follow the flow ... That being said, I still see the issue with the latest snapshot gcc (GCC) 12.0.0 20210613 (experimental) ./dgehd2 INFO =0

[Bug target/101053] Incorrect code at -O1 on arm64

2021-06-13 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101053 --- Comment #3 from Gilles Gouaillardet --- Thanks for the clarification about which registers have to be preserved. I will dig this a bit more from now

[Bug fortran/101053] New: Incorrect code at -O1 on arm64

2021-06-13 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 51003 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51003=edit A simple reproducer This issue was initially reported at https://github.com/nu

[Bug c++/100381] New: new static_assert((std::__is_complete_or_unbounded(...)) failure from g++ 11.1.0

2021-05-02 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 50732 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50732=e

[Bug target/100305] [10 Regression] aarch64: ICE in output_operand_lossage with -O3

2021-04-29 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100305 --- Comment #13 from Gilles Gouaillardet --- Thanks Richard for the quick fix. I am happy to confirm that the latest trunk passes the three reproducers included in this ticket. However, the latest gcc-11 branch only passes the mini

[Bug target/100305] [11/12 Regression] aarch64: ICE in output_operand_lossage with -O3

2021-04-28 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100305 --- Comment #4 from Gilles Gouaillardet --- Thanks Alex for the more minimal reproducer. Sadly, the just released GCC 11.1.0 crashed with this code.

[Bug tree-optimization/100284] ICE in operation_could_trap_p with -march=armv8.2-a+sve -O3

2021-04-28 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100284 --- Comment #8 from Gilles Gouaillardet --- I made a mistake when building GCC 11.1.0, and I am happy to make the following correction: GCC 11.1.0 is *not* affected by this issue. The stack trace came from the master branch.

[Bug c++/100305] New: ICE in output_operand_lossage with -march=armv8.2-a -O3

2021-04-28 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 50696 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50696=edit a (compressed) preprocessed reprodu

[Bug tree-optimization/100284] ICE in operation_could_trap_p with -march=armv8.2-a+sve -O3

2021-04-27 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100284 --- Comment #7 from Gilles Gouaillardet --- Created attachment 50695 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50695=edit preprocessed reproducer $ ~/local/gcc-11.1.0/bin/gcc -march=armv8.2-a+sve -O3 -c bug.i The bug has been

[Bug c/100284] New: gcc crash with -march=armv8.2-a+sve -O3

2021-04-27 Thread gilles.gouaillardet at gmail dot com via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 50686 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50686=edit a reproducer The attached (and self-contained) bug.c (trimmed from GROMACS 202

[Bug fortran/97046] Bad interaction between lbound/ubound, allocatable arrays and bind(C) subroutine with dimension(..) parameter

2020-09-14 Thread gilles.gouaillardet at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97046 --- Comment #4 from Gilles Gouaillardet --- I crafted the reproducer based on a previous one that has already been merged, and using a libc subroutine was not an issue back then.

[Bug fortran/97046] Bad interaction between lbound/ubound, allocatable arrays and bind(C) subroutine with dimension(..) parameter

2020-09-14 Thread gilles.gouaillardet at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97046 Gilles Gouaillardet changed: What|Removed |Added CC||gilles.gouaillardet at gmail dot

[Bug gcov-profile/67097] gcov-tool merge (can) crash when dir2 contains files not in dir1

2016-08-15 Thread gilles.gouaillardet at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67097 Gilles Gouaillardet changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Bug gcov-profile/67097] gcov-tool merge (can) crash when dir2 contains files not in dir1

2016-08-08 Thread gilles.gouaillardet at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67097 --- Comment #6 from Gilles Gouaillardet --- as a side note, would you be interested in me providing a patch so gcov-tool merge can merge n directories (currently, we are limited to n=2) ? i would implement that via a binary tree, so under the

[Bug gcov-profile/67097] gcov-tool merge (can) crash when dir2 contains files not in dir1

2016-08-08 Thread gilles.gouaillardet at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67097 Gilles Gouaillardet changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Bug gcov-profile/67097] gcov-tool merge (can) crash when dir2 contains files not in dir1

2016-08-04 Thread gilles.gouaillardet at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67097 --- Comment #3 from Gilles Gouaillardet --- Shall I try again with the latest snapshot instead ? I am not very familiar with building from svn...

[Bug libgcc/67097] New: gcov-tool merge (can) crash when dir2 contains files not in dir1

2015-08-03 Thread gilles.gouaillardet at gmail dot com
Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 36109 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36109action=edit a patch for libgcc/libgcov