public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103248] ICE in operation_could_trap_helper_p, at tree-eh.c:2479
Date: Mon, 15 Nov 2021 12:54:30 +0000	[thread overview]
Message-ID: <bug-103248-4-RmejaBlxsl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103248-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #3)
> With just -ftrivial-auto-var-init=pattern I see and ICE in
> 
> during GIMPLE pass: lower
> vbase8-22.C: In function 'int main()':
> vbase8-22.C:69:1: internal compiler error: in clear_padding_type, at
> gimple-fold.c:4804
> 0x12d6a63 clear_padding_type
>         /home/rguenther/src/trunk/gcc/gimple-fold.c:4804
> 0x12d69da clear_padding_type
>         /home/rguenther/src/trunk/gcc/gimple-fold.c:4799
> 0x12d7b91 gimple_fold_builtin_clear_padding
>         /home/rguenther/src/trunk/gcc/gimple-fold.c:5006
> 0x12d8335 gimple_fold_builtin
>         /home/rguenther/src/trunk/gcc/gimple-fold.c:5180
> 0x12da469 gimple_fold_call
>         /home/rguenther/src/trunk/gcc/gimple-fold.c:5588
> 
> cut&pasting all arguments you list doesn't change that, so ...?  How did you
> configure GCC?  I have --target=arm-none-linux-gnueabihf --with-float=hard
> --with-cpu=cortex-a9 --with-fpu=neon-fp16

I've filed PR103249 for the above.

  parent reply	other threads:[~2021-11-15 12:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 11:11 [Bug target/103248] New: " marxin at gcc dot gnu.org
2021-11-15 11:21 ` [Bug target/103248] " pinskia at gcc dot gnu.org
2021-11-15 11:24 ` marxin at gcc dot gnu.org
2021-11-15 12:12 ` rguenth at gcc dot gnu.org
2021-11-15 12:16 ` marxin at gcc dot gnu.org
2021-11-15 12:26 ` rguenth at gcc dot gnu.org
2021-11-15 12:33 ` marxin at gcc dot gnu.org
2021-11-15 12:54 ` jakub at gcc dot gnu.org [this message]
2021-11-16  9:26 ` rguenth at gcc dot gnu.org
2021-11-16  9:30 ` marxin at gcc dot gnu.org
2021-11-16  9:30 ` marxin at gcc dot gnu.org
2021-11-16 10:44 ` [Bug middle-end/103248] " rguenth at gcc dot gnu.org
2021-11-16 12:49 ` [Bug middle-end/103248] [12 Regression] " rguenth at gcc dot gnu.org
2021-11-17  0:32 ` joseph at codesourcery dot com
2021-11-19  8:36 ` cvs-commit at gcc dot gnu.org
2021-11-19  8:36 ` rguenth at gcc dot gnu.org
2021-11-22  8:00 ` cvs-commit at gcc dot gnu.org
2022-02-17 10:48 ` cvs-commit at gcc dot gnu.org
2022-02-17 11:57 ` cvs-commit 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-103248-4-RmejaBlxsl@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).