public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99033] New: [11 Regression] ICE in tree_to_poly_int64, at tree.c:3091
Date: Tue, 09 Feb 2021 17:39:13 +0000	[thread overview]
Message-ID: <bug-99033-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99033
           Summary: [11 Regression] ICE in tree_to_poly_int64, at
                    tree.c:3091
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Behavior of release versions changed between 20200517 and 20200524 :


$ cat z1.cc
struct S {
  char c;
  struct T {} T::*b[];
} a;

void f ()
{
  a.c = 1;
}


$ g++-11-20200517 -c z1.cc -fsanitize=undefined
$
$ g++-11-20210207 -c z1.cc -fsanitize=undefined
during GIMPLE pass: ubsan
z1.cc: In function 'void f()':
z1.cc:9:1: internal compiler error: in tree_to_poly_int64, at tree.c:3091
    9 | }
      | ^
0xf4bbe8 tree_to_poly_int64(tree_node const*)
        ../../gcc/tree.c:3091
0xf68db4 component_ref_size(tree_node*, special_array_member*)
        ../../gcc/tree.c:13909
0xd6eb12 decl_init_size(tree_node*, bool)
        ../../gcc/tree-object-size.c:196
0xd6f062 addr_object_size
        ../../gcc/tree-object-size.c:285
0xd70583 compute_builtin_object_size(tree_node*, int, unsigned long*,
tree_node**, tree_node**)
        ../../gcc/tree-object-size.c:570
0xcf945a instrument_object_size
        ../../gcc/ubsan.c:2150
0xcfe535 execute
        ../../gcc/ubsan.c:2405

             reply	other threads:[~2021-02-09 17:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 17:39 gscfq@t-online.de [this message]
2021-02-09 17:39 ` [Bug c++/99033] " gscfq@t-online.de
2021-02-09 17:57 ` [Bug c++/99033] [9/10/11 " mpolacek at gcc dot gnu.org
2021-02-10  7:21 ` rguenth at gcc dot gnu.org
2021-02-10 14:24 ` jakub at gcc dot gnu.org
2021-02-11 16:25 ` cvs-commit at gcc dot gnu.org
2021-02-11 16:26 ` [Bug c++/99033] [9/10 " jakub at gcc dot gnu.org
2021-03-19 23:29 ` cvs-commit at gcc dot gnu.org
2021-03-20  8:07 ` [Bug c++/99033] [9 " jakub at gcc dot gnu.org
2021-04-20 23:32 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:50 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:11 ` jakub 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-99033-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).