public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110332] [14 regression] ICE in dominated_by_p when building LLVM with -O3
Date: Wed, 21 Jun 2023 17:05:29 +0000	[thread overview]
Message-ID: <bug-110332-4-BmWL2edIXf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110332-4@http.gcc.gnu.org/bugzilla/>

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

Sergei Trofimovich <slyfox at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |slyfox at gcc dot gnu.org

--- Comment #6 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
I think I see the same ICE on llvm-12 and r14-2009-g864c6471bdc6cd:

cvise produced this thing:

// $ cat a.cpp.cpp
struct SlotIndex { int lie; };
SlotIndex si7, si8;

unsigned u9, u6;
bool b3, b4;
unsigned &value() {
  return b4 ? u6 : u9;
}
void transferValues() {
  unsigned RegIdx;
  SlotIndex End;
  RegIdx = value();
  End = b3 ? si7 : si8;
}

$ g++ -O3  -c a.cpp.cpp -o a.o
during GIMPLE pass: phiprop
a.cpp.cpp: In function 'void transferValues()':
a.cpp.cpp:14:1: internal compiler error: Segmentation fault
   14 | }
      | ^
0x1d74824 diagnostic_impl(rich_location*, diagnostic_metadata const*, int, char
const*, __va_list_tag (*) [1], diagnostic_t)
        ???:0
0x1d74d97 internal_error(char const*, ...)
        ???:0
0xe9bfdf crash_signal(int)
        ???:0
0xa851da dominated_by_p(cdi_direction, basic_block_def const*, basic_block_def
const*)
        ???:0
0x102096b (anonymous namespace)::pass_phiprop::execute(function*)
        ???:0

$ g++  -v
Using built-in specs.
COLLECT_GCC=/<<NIX>>/gcc-14.0.0/bin/g++
COLLECT_LTO_WRAPPER=/<<NIX>>/gcc-14.0.0/libexec/gcc/x86_64-unknown-linux-gnu/14.0.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: 
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 99999999 (experimental) (GCC)

  parent reply	other threads:[~2023-06-21 17:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21  4:57 [Bug tree-optimization/110332] New: " sjames at gcc dot gnu.org
2023-06-21  4:59 ` [Bug tree-optimization/110332] " sjames at gcc dot gnu.org
2023-06-21  5:00 ` pinskia at gcc dot gnu.org
2023-06-21  5:07 ` pinskia at gcc dot gnu.org
2023-06-21  5:19 ` pinskia at gcc dot gnu.org
2023-06-21  8:36 ` rguenth at gcc dot gnu.org
2023-06-21 16:57 ` sjames at gcc dot gnu.org
2023-06-21 17:05 ` slyfox at gcc dot gnu.org [this message]
2023-06-21 17:11 ` pinskia at gcc dot gnu.org
2023-06-21 20:55 ` pinskia at gcc dot gnu.org
2023-06-22  6:08 ` slyfox at gcc dot gnu.org
2023-06-22  6:40 ` rguenth at gcc dot gnu.org
2023-06-22  8:14 ` cvs-commit at gcc dot gnu.org
2023-06-22  8:14 ` rguenth at gcc dot gnu.org
2023-06-22  9:55 ` slyfox 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-110332-4-BmWL2edIXf@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).