public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/99194] New: [11 Regression] ICE in force_constant_size, at gimplify.c:733 since r11-38-g375a77925c320a27
Date: Mon, 22 Feb 2021 10:18:43 +0000	[thread overview]
Message-ID: <bug-99194-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99194
           Summary: [11 Regression] ICE in force_constant_size, at
                    gimplify.c:733 since r11-38-g375a77925c320a27
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: jamborm at gcc dot gnu.org, marxin at gcc dot gnu.org,
                    rguenth at gcc dot gnu.org
  Target Milestone: ---

The following fails:

$ gcc /home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr99122-3.c -Os -c
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr99122-3.c:13:20: warning:
‘struct T’ declared inside parameter list will not be visible outside of this
definition or declaration
   13 | foo (int n, struct T { char a[n]; } b)
      |                    ^
In function ‘foo.constprop’:
cc1: internal compiler error: in force_constant_size, at gimplify.c:733
0x6ac5ac force_constant_size
        /home/marxin/Programming/gcc/gcc/gimplify.c:733
0xbac087 gimple_add_tmp_var(tree_node*)
        /home/marxin/Programming/gcc/gcc/gimplify.c:771
0xb74c8e create_tmp_var(tree_node*, char const*)
        /home/marxin/Programming/gcc/gcc/gimple-expr.c:485
0xbc0fdb create_tmp_from_val
        /home/marxin/Programming/gcc/gcc/gimplify.c:564
0xbc0fdb lookup_tmp_var
        /home/marxin/Programming/gcc/gcc/gimplify.c:596
0xbc0fdb internal_get_tmp_var
        /home/marxin/Programming/gcc/gcc/gimplify.c:635
0xbb973e gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
        /home/marxin/Programming/gcc/gcc/gimplify.c:15070
0xbd6a61 gimple_regimplify_operands(gimple*, gimple_stmt_iterator*)
        /home/marxin/Programming/gcc/gcc/gimplify-me.c:235
0xef52ba insert_init_stmt
        /home/marxin/Programming/gcc/gcc/tree-inline.c:3400
0xf078d6 tree_function_versioning(tree_node*, tree_node*, vec<ipa_replace_map*,
va_gc, vl_embed>*, ipa_param_adjustments*, bool, bitmap_head*,
basic_block_def*)
        /home/marxin/Programming/gcc/gcc/tree-inline.c:6430
0xa0d0b0 cgraph_node::materialize_clone()
        /home/marxin/Programming/gcc/gcc/cgraphclones.c:1131
0x9fa9fd cgraph_node::get_untransformed_body()
        /home/marxin/Programming/gcc/gcc/cgraph.c:3903
0xa06dd1 cgraph_node::expand()
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:1798
0xa0852e expand_all_functions
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:1995
0xa0852e symbol_table::compile()
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:2359
0xa0852e symbol_table::compile()
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:2270
0xa0b167 symbol_table::finalize_compilation_unit()
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:2540
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-02-22 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 10:18 marxin at gcc dot gnu.org [this message]
2021-02-22 10:19 ` [Bug ipa/99194] " marxin at gcc dot gnu.org
2021-02-22 10:19 ` marxin at gcc dot gnu.org
2021-02-22 12:51 ` rguenth at gcc dot gnu.org
2021-02-26 11:55 ` rguenth at gcc dot gnu.org
2021-03-04 14:22 ` jamborm 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-99194-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).