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++/108543] New: ICE in build_call_expr_loc_array, at tree.cc:10686
Date: Wed, 25 Jan 2023 17:47:54 +0000	[thread overview]
Message-ID: <bug-108543-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108543
           Summary: ICE in build_call_expr_loc_array, at tree.cc:10686
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started with r8 :


$ cat z1.cc
#include <vector>


$ g++-13-20230122 -c z1.cc -fsanitize=address -fno-sanitize=kernel-address
-fsanitize=pointer-subtract
In file included from .../gcc-13-20230122/include/c++/13.0.1/vector:67,
                 from z1.cc:1:
.../gcc-13-20230122/include/c++/13.0.1/bits/stl_bvector.h: In function
'std::ptrdiff_t std::operator-(const _Bit_iterator_base&, const
_Bit_iterator_base&)':
.../gcc-13-20230122/include/c++/13.0.1/bits/stl_bvector.h:269:50: internal
compiler error: Segmentation fault
  269 |       return (int(_S_word_bit) * (__x._M_p - __y._M_p)
      |                                                  ^~~~
0xeb575f crash_signal
        ../../gcc/toplev.cc:314
0x114833e build_call_expr_loc_array(unsigned int, tree_node*, int, tree_node**)
        ../../gcc/tree.cc:10686
0x114842f build_call_expr_loc(unsigned int, tree_node*, int, ...)
        ../../gcc/tree.cc:10719
0x98b393 pointer_diff
        ../../gcc/cp/typeck.cc:6728
0x98b393 cp_build_binary_op(op_location_t const&, tree_code, tree_node*,
tree_node*, int)
        ../../gcc/cp/typeck.cc:5350
0x7c8c8c build_new_op(op_location_t const&, tree_code, int, tree_node*,
tree_node*, tree_node*, tree_node*, tree_node**, int)
        ../../gcc/cp/call.cc:7369
0x97de10 build_x_binary_op(op_location_t const&, tree_code, tree_node*,
tree_code, tree_node*, tree_code, tree_node*, tree_node**, int)
        ../../gcc/cp/typeck.cc:4722
0x8d16e3 cp_parser_binary_expression
        ../../gcc/cp/parser.cc:10283
0x8d1eb4 cp_parser_assignment_expression
        ../../gcc/cp/parser.cc:10444
0x8d35f2 cp_parser_expression
        ../../gcc/cp/parser.cc:10614
0x8e50c1 cp_parser_primary_expression
        ../../gcc/cp/parser.cc:5722
0x8e8a76 cp_parser_postfix_expression
        ../../gcc/cp/parser.cc:7731
0x8fbfff cp_parser_unary_expression
        ../../gcc/cp/parser.cc:9095
0x8d0bff cp_parser_cast_expression
        ../../gcc/cp/parser.cc:9999
0x8d190c cp_parser_simple_cast_expression
        ../../gcc/cp/parser.cc:32523
0x8d190c cp_parser_binary_expression
        ../../gcc/cp/parser.cc:10168
0x8d1eb4 cp_parser_assignment_expression
        ../../gcc/cp/parser.cc:10444
0x8d35f2 cp_parser_expression
        ../../gcc/cp/parser.cc:10614
0x8e50c1 cp_parser_primary_expression
        ../../gcc/cp/parser.cc:5722
0x8e8a76 cp_parser_postfix_expression
        ../../gcc/cp/parser.cc:7731

             reply	other threads:[~2023-01-25 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 17:47 gscfq@t-online.de [this message]
2023-01-25 18:30 ` [Bug c++/108543] [10/11/12/13 Regression] " mpolacek at gcc dot gnu.org
2023-01-25 18:46 ` mpolacek at gcc dot gnu.org
2023-01-25 18:49 ` mpolacek at gcc dot gnu.org
2023-01-25 19:27 ` mpolacek at gcc dot gnu.org
2023-01-26 17:59 ` [Bug middle-end/108543] " cvs-commit at gcc dot gnu.org
2023-01-26 18:39 ` cvs-commit at gcc dot gnu.org
2023-01-26 18:46 ` [Bug middle-end/108543] [10/11 " 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-108543-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).