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/96610] ICE: in gimplify_va_arg_expr, at gimplify.c:15150
Date: Fri, 14 Aug 2020 01:00:48 +0000	[thread overview]
Message-ID: <bug-96610-4-yCcgqT6u2R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96610-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[11 Regression] ICE: in     |ICE: in
                   |gimplify_va_arg_expr, at    |gimplify_va_arg_expr, at
                   |gimplify.c:15150            |gimplify.c:15150
           Keywords|                            |ice-checking,
                   |                            |ice-on-invalid-code

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>test.c:8: confused by earlier errors, bailing out

It was ICEing in GCC 10, just with --enable-checking=release causes the above
message to be printed out instead of a full ICE.

  reply	other threads:[~2020-08-14  1:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-14  0:39 [Bug c/96610] New: [11 Regression] " anbu1024.me at gmail dot com
2020-08-14  1:00 ` pinskia at gcc dot gnu.org [this message]
2020-08-14  7:39 ` [Bug c/96610] ICE: in gimplify_va_arg_expr, at gimplify.c:15150 since r7-2847-gba9bbd6f584afe29 marxin at gcc dot gnu.org
2022-01-03 20:52 ` [Bug c/96610] [9/10 Regression] " pinskia at gcc dot gnu.org
2022-01-03 20:54 ` pinskia 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-96610-4-yCcgqT6u2R@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).