public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rafaelcfsousa at ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/104894] New: [ppc64le] gcc11 ICE with -fno-plt Date: Sat, 12 Mar 2022 14:45:31 +0000 [thread overview] Message-ID: <bug-104894-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104894 Bug ID: 104894 Summary: [ppc64le] gcc11 ICE with -fno-plt Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rafaelcfsousa at ibm dot com Target Milestone: --- When I use the flag "-fno-plt" together with "-O2 -mcpu=power10" on gcc11, the compilation fails. Some important points: - The ICE shows up only when I use optimization level -O2 or higher - If I replace "-mcpu=power10" by "-mcpu=power9", the compilation works fine - The same error does not happen on gcc10 gcc version: - gcc (GCC) 11.2.1 20220312 [remotes/origin/releases/gcc-11 revision 6f581f90e3:53ab7b79c6:908e612067e42ded881db10d38768f23307bf55e] - gcc (GCC) 11.2.1 20220211 (Advance-Toolchain 15.0-2) [64575dfb22ae] - gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-1) - gcc (GCC) 12.0.1 20220312 (experimental) [remotes/origin/HEAD r12-7622-g828335beb7] The error shows up on all GCCs above. the system type: ppc64le (powerpc64le-unknown-linux-gnu) Configured with: /home/gccbuild/gcc_11_git/gcc/configure --prefix=/opt/gcc-nightly/11 --with-as=/home/gccbuild/binutils/install/bin/as --with-ld=/home/gccbuild/binutils/install/bin/ld --enable-languages=c,c++,fortran,objc,obj-c++ --with-cpu=power10 source file: issue.c ``` void foo(); void bar() { foo(); } ``` the complete command line that triggers the bug: gcc -O3 -mcpu=power10 -mtune=power10 -fno-plt -c issue.c -o issue.o the compiler output (error messages, warnings, etc.): during RTL pass: expand issue.c: In function ‘bar’: issue.c:4:4: internal compiler error: in rs6000_sibcall_aix, at config/rs6000/rs6000.cc:25654 4 | foo(); | ^~~~~ 0x11073563 rs6000_sibcall_aix(rtx_def*, rtx_def*, rtx_def*, rtx_def*) /home/gccbuild/gcc_trunk_git/gcc/gcc/config/rs6000/rs6000.cc:25654 0x116acc5f gen_sibcall(rtx_def*, rtx_def*, rtx_def*) /home/gccbuild/gcc_trunk_git/gcc/gcc/config/rs6000/rs6000.md:11573 0x1104f17f target_gen_sibcall /home/gccbuild/gcc_trunk_git/gcc/gcc/config/rs6000/rs6000.md:13266 0x10486a0f emit_call_1 /home/gccbuild/gcc_trunk_git/gcc/gcc/calls.cc:469 0x1048f363 expand_call(tree_node*, rtx_def*, int) /home/gccbuild/gcc_trunk_git/gcc/gcc/calls.cc:3608 0x106614eb expand_expr_real_1(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) /home/gccbuild/gcc_trunk_git/gcc/gcc/expr.cc:11539 0x104b0887 expand_expr /home/gccbuild/gcc_trunk_git/gcc/gcc/expr.h:301 0x104b0887 expand_call_stmt /home/gccbuild/gcc_trunk_git/gcc/gcc/cfgexpand.cc:2831 0x104b0887 expand_gimple_stmt_1 /home/gccbuild/gcc_trunk_git/gcc/gcc/cfgexpand.cc:3869 0x104b0887 expand_gimple_stmt /home/gccbuild/gcc_trunk_git/gcc/gcc/cfgexpand.cc:4033 0x104b850b expand_gimple_tailcall /home/gccbuild/gcc_trunk_git/gcc/gcc/cfgexpand.cc:4079 0x104b850b expand_gimple_basic_block /home/gccbuild/gcc_trunk_git/gcc/gcc/cfgexpand.cc:6054 0x104ba5d7 execute /home/gccbuild/gcc_trunk_git/gcc/gcc/cfgexpand.cc:6806 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. using --save-temps: issue.s ``` .file "issue.c" .machine power10 .abiversion 2 .section ".text" ``` issue.i ``` # 0 "issue.c" # 0 "<built-in>" # 0 "<command-line>" # 1 "/usr/include/stdc-predef.h" 1 3 4 # 0 "<command-line>" 2 # 1 "issue.c" void foo(); void bar() { foo(); } ```
next reply other threads:[~2022-03-12 14:45 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-12 14:45 rafaelcfsousa at ibm dot com [this message] 2022-03-13 7:36 ` [Bug target/104894] [11/12 Regression] ICE with -fno-plt -mcpu=power10 on PowerPC64 LE Linux pinskia at gcc dot gnu.org 2022-03-15 2:28 ` amodra at gmail dot com 2022-03-15 9:02 ` jakub at gcc dot gnu.org 2022-03-22 21:44 ` bergner at gcc dot gnu.org 2022-03-23 1:11 ` amodra at gmail dot com 2022-03-23 12:54 ` rguenth at gcc dot gnu.org 2022-03-24 21:33 ` bergner at gcc dot gnu.org 2022-03-24 23:55 ` amodra at gmail dot com 2022-03-25 0:02 ` amodra at gmail dot com 2022-04-04 22:13 ` bergner at gcc dot gnu.org 2022-04-05 22:07 ` bergner at gcc dot gnu.org 2022-04-11 22:02 ` cvs-commit at gcc dot gnu.org 2022-04-12 20:24 ` cvs-commit at gcc dot gnu.org 2022-04-12 20:32 ` bergner at gcc dot gnu.org
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-104894-4@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: linkBe 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).