Bug 2043040 - ICE with gcc 12 on ppc64le
Summary: ICE with gcc 12 on ppc64le
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2043937 2045121 (view as bug list)
Depends On:
Blocks: F36FTBFS 2045134 2045730 2045821 2045832
TreeView+ depends on / blocked
 
Reported: 2022-01-20 14:20 UTC by Tom Hughes
Modified: 2022-01-27 13:03 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-01-26 23:59:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Preprocessed source code (339.36 KB, application/gzip)
2022-01-20 14:20 UTC, Tom Hughes
no flags Details
Valgrind log (9.38 KB, application/gzip)
2022-01-20 14:21 UTC, Tom Hughes
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNU Compiler Collection 104172 0 P2 NEW [9/10/11/12 Regression] ppc64le mangling ICE with -flto -ffat-lto-objects 2022-01-25 12:28:03 UTC

Description Tom Hughes 2022-01-20 14:20:29 UTC
Created attachment 1852179 [details]
Preprocessed source code

Description of problem:

ICE caused by SEGV during a koji build (https://koji.fedoraproject.org/koji/taskinfo?taskID=81524235) on ppc64le:

cd /builddir/build/BUILD/libosmium-2.17.3/libosmium/redhat-linux-build/examples && /usr/bin/g++ -DOSMIUM_WITH_LZ4 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/builddir/build/BUILD/libosmium-2.17.3/libosmium/include -isystem /usr/include/gdal -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection  -DNDEBUG   -std=c++11 -pthread -MD -MT examples/CMakeFiles/osmium_debug.dir/osmium_debug.cpp.o -MF CMakeFiles/osmium_debug.dir/osmium_debug.cpp.o.d -o CMakeFiles/osmium_debug.dir/osmium_debug.cpp.o -c /builddir/build/BUILD/libosmium-2.17.3/libosmium/examples/osmium_debug.cpp
*** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins.
Event                            | Plugins
PLUGIN_FINISH_UNIT               | annobin: Generate final annotations
PLUGIN_START_UNIT                | annobin: Generate global annotations
PLUGIN_ALL_PASSES_START          | annobin: Generate per-function annotations
PLUGIN_ALL_PASSES_END            | annobin: Register per-function end symbols
during RTL pass: final
In file included from /builddir/build/BUILD/libosmium-2.17.3/libosmium/test/test_main.cpp:2:
/usr/include/catch2/catch.hpp: In member function 'Catch::LazyExpression::LazyExpression(bool)':
/usr/include/catch2/catch.hpp:8185:5: internal compiler error: Segmentation fault
 8185 |     LazyExpression::LazyExpression( bool isNegated )
      |     ^~~~~~~~~~~~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.

Version-Release number of selected component (if applicable):

12.0.1-0.2.fc36

How reproducible:

Two attempts in koji have failed the same way but I have been unable to reproduce it using the ppc64le test machine with the same compiler.

Additional info:

Although I couldn't reproduce it on the test machine running under valgrind did report a number of issues.

I will attach the preprocessed source and the valgrind log.

Comment 1 Tom Hughes 2022-01-20 14:21:06 UTC
Created attachment 1852180 [details]
Valgrind log

Comment 2 Petr Menšík 2022-01-25 11:26:26 UTC
*** Bug 2043937 has been marked as a duplicate of this bug. ***

Comment 3 Tom Hughes 2022-01-25 16:45:50 UTC
*** Bug 2045121 has been marked as a duplicate of this bug. ***

Comment 4 Jaroslav Škarvada 2022-01-26 09:57:27 UTC
There are possible duplicates bug 2043246, bug 2042668.


Note You need to log in before you can comment on or make changes to this bug.