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/99324] New: ICE in mark_addressable, at gimple-expr.c:918
Date: Mon, 01 Mar 2021 17:05:49 +0000	[thread overview]
Message-ID: <bug-99324-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99324
           Summary: ICE in mark_addressable, at gimple-expr.c:918
           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: ---

Affects versions down to r6, with missing ";" at /// :


$ cat z1.c
#include <stdarg.h>
void f (int x, ...)
{
  va_list a;
  va_arg (a, int);
  int b () ///;
  int c[va_arg (a, int)];
  va_end (a);
  return;
}


$ gcc-11-20210228 -c z1.c
z1.c: In function 'b':
z1.c:7:3: internal compiler error: Segmentation fault
    7 |   int c[va_arg (a, int)];
      |   ^~~
0xb5eeff crash_signal
        ../../gcc/toplev.c:327
0x8c6733 mark_addressable(tree_node*)
        ../../gcc/gimple-expr.c:918
0x6ce03c build_va_arg(unsigned int, tree_node*, tree_node*)
        ../../gcc/c-family/c-common.c:4630
0x6751b6 c_parser_postfix_expression
        ../../gcc/c/c-parser.c:9141
0x67e012 c_parser_unary_expression
        ../../gcc/c/c-parser.c:8224
0x67f03f c_parser_cast_expression
        ../../gcc/c/c-parser.c:8066
0x67f2f9 c_parser_binary_expression
        ../../gcc/c/c-parser.c:7869
0x680305 c_parser_conditional_expression
        ../../gcc/c/c-parser.c:7592
0x680861 c_parser_expr_no_commas
        ../../gcc/c/c-parser.c:7507
0x67d1f6 c_parser_direct_declarator_inner
        ../../gcc/c/c-parser.c:4095
0x694483 c_parser_declaration_or_fndef
        ../../gcc/c/c-parser.c:2148
0x695709 c_parser_declaration_or_fndef
        ../../gcc/c/c-parser.c:2498
0x693bb9 c_parser_compound_statement_nostart
        ../../gcc/c/c-parser.c:5700
0x693ff3 c_parser_compound_statement
        ../../gcc/c/c-parser.c:5597
0x6958a8 c_parser_declaration_or_fndef
        ../../gcc/c/c-parser.c:2539
0x69c717 c_parser_external_declaration
        ../../gcc/c/c-parser.c:1777
0x69d239 c_parser_translation_unit
        ../../gcc/c/c-parser.c:1650
0x69d239 c_parse_file()
        ../../gcc/c/c-parser.c:21984
0x6ed0a2 c_common_parse_file()
        ../../gcc/c-family/c-opts.c:1218

             reply	other threads:[~2021-03-01 17:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 17:05 gscfq@t-online.de [this message]
2021-03-02  7:42 ` [Bug c/99324] " rguenth at gcc dot gnu.org
2021-03-02  9:45 ` [Bug c/99324] [8/9/10/11 Regression] ICE in mark_addressable, at gimple-expr.c:918 since r6-314 jakub at gcc dot gnu.org
2021-03-02 10:02 ` jakub at gcc dot gnu.org
2021-03-02 10:27 ` rguenth at gcc dot gnu.org
2021-03-02 11:30 ` jakub at gcc dot gnu.org
2021-03-03  8:55 ` cvs-commit at gcc dot gnu.org
2021-03-03  8:58 ` [Bug c/99324] [8/9/10 " jakub at gcc dot gnu.org
2021-03-19 23:30 ` cvs-commit at gcc dot gnu.org
2021-03-20  8:09 ` [Bug c/99324] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:33 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:51 ` 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-99324-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).