public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100574] New: [11/12 Regression] ICE: in size_remaining, at builtins.c:413 with -O3 -ftracer -fno-tree-dominator-opts -fno-tree-fre
Date: Wed, 12 May 2021 19:57:16 +0000	[thread overview]
Message-ID: <bug-100574-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 100574
           Summary: [11/12 Regression] ICE: in size_remaining, at
                    builtins.c:413 with -O3 -ftracer
                    -fno-tree-dominator-opts -fno-tree-fre
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu

Created attachment 50802
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50802&action=edit
auto-reduced testcase (from OpenTTD sources)

Compiler output:
$ x86_64-pc-linux-gnu-gcc -O3 -ftracer -fno-tree-dominator-opts -fno-tree-fre
testcase.C 
during GIMPLE pass: strlen
testcase.C: In function 'void ReadTrackChunk()':
testcase.C:43:6: internal compiler error: in size_remaining, at builtins.c:413
   43 | void ReadTrackChunk() {
      |      ^~~~~~~~~~~~~~
0x714a5d
access_ref::size_remaining(generic_wide_int<fixed_wide_int_storage<128> >*)
const
        /repo/gcc-trunk/gcc/builtins.c:413
0xe2f36a access_ref::add_offset(generic_wide_int<fixed_wide_int_storage<128> >
const&, generic_wide_int<fixed_wide_int_storage<128> > const&)
        /repo/gcc-trunk/gcc/builtins.c:517
0xe30211 handle_mem_ref
        /repo/gcc-trunk/gcc/builtins.c:5407
0xe30211 compute_objsize_r
        /repo/gcc-trunk/gcc/builtins.c:5549
0xe335d2 compute_objsize(tree_node*, int, access_ref*, pointer_query*)
        /repo/gcc-trunk/gcc/builtins.c:5816
0x1514411 maybe_warn_overflow
        /repo/gcc-trunk/gcc/tree-ssa-strlen.c:1952
0x151cbe1 maybe_warn_overflow
        /repo/gcc-trunk/gcc/tree-ssa-strlen.c:2096
0x151cbe1 handle_store
        /repo/gcc-trunk/gcc/tree-ssa-strlen.c:4788
0x151f4a6 check_and_optimize_stmt
        /repo/gcc-trunk/gcc/tree-ssa-strlen.c:5426
0x151f4a6 strlen_dom_walker::before_dom_children(basic_block_def*)
        /repo/gcc-trunk/gcc/tree-ssa-strlen.c:5622
0x1dcfc57 dom_walker::walk(basic_block_def*)
        /repo/gcc-trunk/gcc/domwalk.c:309
0x1514f1e printf_strlen_execute
        /repo/gcc-trunk/gcc/tree-ssa-strlen.c:5688
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

             reply	other threads:[~2021-05-12 19:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 19:57 zsojka at seznam dot cz [this message]
2021-05-12 23:12 ` [Bug tree-optimization/100574] " msebor at gcc dot gnu.org
2021-05-13  1:58 ` msebor at gcc dot gnu.org
2021-05-13 22:33 ` cvs-commit at gcc dot gnu.org
2021-05-13 22:39 ` [Bug tree-optimization/100574] [11 " msebor at gcc dot gnu.org
2021-05-17 11:35 ` rguenth at gcc dot gnu.org
2021-06-17 20:07 ` cvs-commit at gcc dot gnu.org
2021-06-17 20:09 ` msebor 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-100574-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).