public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/115476] [13/14/15 Regression] __has_unique_object_representation ICE with array of uninstantiated type of unknown bound
Date: Thu, 13 Jun 2024 15:20:20 +0000	[thread overview]
Message-ID: <bug-115476-4-t2BDXNJ4ZF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115476-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
           Keywords|                            |ice-on-valid-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2024-06-13
            Summary|__has_unique_object_represe |[13/14/15 Regression]
                   |ntation ICE with array of   |__has_unique_object_represe
                   |uninstantiated type of      |ntation ICE with array of
                   |unknown bound               |uninstantiated type of
                   |                            |unknown bound
      Known to work|                            |12.3.0
      Known to fail|                            |13.1.0
   Target Milestone|---                         |13.4

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed. full backtrace:
```
t.cc:6:59: internal compiler error: Segmentation fault
    6 |     auto t = (__has_unique_object_representations(Foo<0>[]));
      |                                                           ^
0x137448f crash_signal
        /home/apinski/src/upstream-gcc-new/gcc/gcc/toplev.cc:319
0xce7df0 contains_struct_check(tree_node const*, tree_node_structure_enum, char
const*, int, char const*)
        /home/apinski/src/upstream-gcc-new/gcc/gcc/tree.h:4065
0xce7df0 wi::extended_tree<128>::extended_tree(tree_node const*)
        /home/apinski/src/upstream-gcc-new/gcc/gcc/tree.h:6477
0xce7df0 generic_wide_int<wi::extended_tree<128> >::generic_wide_int<tree_node
const*>(tree_node const* const&)
        /home/apinski/src/upstream-gcc-new/gcc/gcc/wide-int.h:847
0xce7df0 wi::to_offset(tree_node const*)
        /home/apinski/src/upstream-gcc-new/gcc/gcc/tree.h:6429
0xce7df0 record_has_unique_obj_representations
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/tree.cc:4832
0xce77bb type_has_unique_obj_representations(tree_node const*)
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/tree.cc:4747
0xcc782e finish_trait_expr(unsigned int, cp_trait_kind, tree_node*, tree_node*)
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/semantics.cc:13074
0xc2db09 cp_parser_trait
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:11314
0xc1de71 cp_parser_postfix_expression
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:7954
0xbf4c10 cp_parser_binary_expression
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:10413
0xbf59f4 cp_parser_assignment_expression
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:10757
0xbf5fa4 cp_parser_expression
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:10924
0xc08ebd cp_parser_primary_expression
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:5945
0xc1de71 cp_parser_postfix_expression
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:7954
0xbf4c10 cp_parser_binary_expression
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:10413
0xbf59f4 cp_parser_assignment_expression
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:10757
0xbf7b8e cp_parser_constant_expression
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:11047
0xbf97c6 cp_parser_initializer_clause
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:26369
0xbfcfd4 cp_parser_initializer
        /home/apinski/src/upstream-gcc-new/gcc/gcc/cp/parser.cc:26308
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.

```

  reply	other threads:[~2024-06-13 15:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 15:08 [Bug c++/115476] New: " mital at mitalashok dot co.uk
2024-06-13 15:20 ` pinskia at gcc dot gnu.org [this message]
2024-06-13 15:36 ` [Bug c++/115476] [13/14/15 Regression] " mpolacek at gcc dot gnu.org
2024-06-13 15:45 ` mpolacek at gcc dot gnu.org
2024-06-13 15:52 ` mital at mitalashok dot co.uk
2024-06-13 15:56 ` mital at mitalashok dot co.uk
2024-06-13 16:22 ` mpolacek at gcc dot gnu.org
2024-06-13 16:26 ` mpolacek at gcc dot gnu.org
2024-06-13 18:14 ` mital at mitalashok dot co.uk
2024-06-18 14:39 ` mpolacek at gcc dot gnu.org
2024-06-25 21:45 ` cvs-commit at gcc dot gnu.org
2024-06-25 21:46 ` [Bug c++/115476] [13/14 " mpolacek 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-115476-4-t2BDXNJ4ZF@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).