public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/108713] ICE during RTL pass: into_cfglayout for x86_64-pc-linux-gnu '-m32', C++ 'libgomp.c-c++-common/for-11.c'
Date: Wed, 29 Mar 2023 21:23:42 +0000	[thread overview]
Message-ID: <bug-108713-4-zIJkpw3OJ1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108713-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108713

--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(Possibly?) similarly now with GCC sources based on 2023-03-28 commit
b3c5933ee726004e4e47291d422dfe7ac3345062, with a bunch of local OMP changes on
top (but those shouldn't be touching the relevant area of code), standard
bootstrap build, I've observed an ICE as follows on our x86_64-pc-linux-gnu
testing system amd_ryzen3, in routine libgomp testing for '-m32':

    [...]
    spawn -ignore SIGHUP gcc -x c++
../source-gcc/libgomp/testsuite/libgomp.c++/../libgomp.c-c++-common/for-5.c
-m32 -foffload-options=amdgcn-amdhsa=-march=gfx906
-I../source-gcc/libgomp/testsuite/../../include
-I../source-gcc/libgomp/testsuite/.. -fmessage-length=0
-fno-diagnostics-show-caret -fdiagnostics-color=never -fopenmp -O2 -lstdc++ -lm
-o ./for-5.exe
    during RTL pass: reload
    In file included from
../source-gcc/libgomp/testsuite/libgomp.c++/../libgomp.c-c++-common/for-1.h:18,
                     from
../source-gcc/libgomp/testsuite/libgomp.c++/../libgomp.c-c++-common/for-5.c:50:
   
../source-gcc/libgomp/testsuite/libgomp.c++/../libgomp.c-c++-common/for-2.h: In
function 'f8_tpf_simd_guided32() [clone ._omp_fn.1]':
   
../source-gcc/libgomp/testsuite/libgomp.c++/../libgomp.c-c++-common/for-2.h:127:29:
internal compiler error: Segmentation fault
    0x16a1b7f crash_signal
            [...]/source-gcc/gcc/toplev.cc:314
    0x129c1eb base_pool_allocator<memory_block_pool>::remove(void*)
            [...]/source-gcc/gcc/alloc-pool.h:445
    0x129c1eb object_allocator<et_node>::remove(et_node*)
            [...]/source-gcc/gcc/alloc-pool.h:524
    0x129c1eb et_free_tree_force
            [...]/source-gcc/gcc/et-forest.cc:502
    0x1214868 free_dominance_info(function*, cdi_direction)
            [...]/source-gcc/gcc/dominance.cc:812
    0x1484b08 do_reload
            [...]/source-gcc/gcc/ira.cc:5955
    0x1484b08 execute
            [...]/source-gcc/gcc/ira.cc:6149
    Please submit a full bug report, with preprocessed source (by using
-freport-bug).
    Please include the complete backtrace with any bug report.
    See <https://gcc.gnu.org/bugs/> for instructions.
    compiler exited with status 1
    FAIL: libgomp.c++/../libgomp.c-c++-common/for-5.c (internal compiler error:
Segmentation fault)
    [...]


(In reply to Thomas Schwinge from comment #2)
> (In reply to Jakub Jelinek from comment #1)
> > If you can reproduce it with vanilla trunk, it is worth it, sure, but
> > without a reliable reproducer there isn't much to do.
> 
> I'll attempt to reproduce with clean sources, and Valgrind enabled.

Have not yet gotten to that.

      parent reply	other threads:[~2023-03-29 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08  8:55 [Bug rtl-optimization/108713] New: " tschwinge at gcc dot gnu.org
2023-02-08  9:05 ` [Bug rtl-optimization/108713] " jakub at gcc dot gnu.org
2023-02-08  9:17 ` tschwinge at gcc dot gnu.org
2023-03-29 21:23 ` tschwinge at gcc dot gnu.org [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-108713-4-zIJkpw3OJ1@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).