public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107229] New: ICE at -O1 and -Os with "-ftree-vectorize": verify_gimple failed
Date: Wed, 12 Oct 2022 07:27:52 +0000	[thread overview]
Message-ID: <bug-107229-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107229
           Summary: ICE at -O1 and -Os with "-ftree-vectorize":
                    verify_gimple failed
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zhendong.su at inf dot ethz.ch
  Target Milestone: ---

This appears to be a very recent regression as it doesn't seem to fail with the
build from Compiler Explorer. 

[541] % gcctk -v
Using built-in specs.
COLLECT_GCC=gcctk
COLLECT_LTO_WRAPPER=/local/suz-local/software/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/13.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-trunk/configure --disable-bootstrap
--enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
--with-system-zlib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20221012 (experimental) [master r13-3246-g1c0670c62fc] (GCC) 
[542] % 
[542] % gcctk -O1 small.c; ./a.out
[543] % 
[543] % gcctk -O1 -ftree-vectorize small.c
small.c: In function ‘main’:
small.c:9:5: error: invalid position or size operand to ‘bit_field_ref’
    9 | int main() {
      |     ^~~~
_ifc__17 = BIT_FIELD_REF <_ifc__16, 21, 0xffffffffffffffffffffffffffffffc0>;
during GIMPLE pass: ifcvt
small.c:9:5: internal compiler error: verify_gimple failed
0xf3b99a verify_gimple_in_cfg(function*, bool)
        ../../gcc-trunk/gcc/tree-cfg.cc:5649
0xdf9d17 execute_function_todo
        ../../gcc-trunk/gcc/passes.cc:2091
0xdfa2bb execute_todo
        ../../gcc-trunk/gcc/passes.cc:2145
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.
[544] % 
[544] % cat small.c
int a, c;
struct {
  long d;
  int : 8;
  int : 27;
  int e : 21;
} f;
void g(int b) { a = a & 1; }
int main() {
  while (c)
    g(f.e);
  return 0;
}

             reply	other threads:[~2022-10-12  7:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12  7:27 zhendong.su at inf dot ethz.ch [this message]
2022-10-12  8:04 ` [Bug tree-optimization/107229] [13 Regression] ICE at -O1 and -Os with "-ftree-vectorize": verify_gimple failed since r13-3219-g25413fdb2ac24933 marxin at gcc dot gnu.org
2022-10-12  9:26 ` avieira at gcc dot gnu.org
2022-10-12 16:23 ` law at gcc dot gnu.org
2022-10-13  9:15 ` marxin at gcc dot gnu.org
2022-10-13 11:11 ` cvs-commit at gcc dot gnu.org
2022-10-14  7:19 ` rguenth at gcc dot gnu.org
2022-10-14  7:20 ` rguenth at gcc dot gnu.org
2022-10-14  7:27 ` rguenth 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-107229-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: 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).