public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99679] [11 Regression] ICE in construct_container at gcc/config/i386/i386.c:2571 since g:5e2eabe1eed1e53d39923517122d3c7de2013ad4
Date: Sat, 20 Mar 2021 17:12:11 +0000	[thread overview]
Message-ID: <bug-99679-4-W43h1fE4c3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99679-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

https://gcc.gnu.org/g:19ff0b0d816e6e7d7657a8559e9957d79dc1d77f

commit r11-7751-g19ff0b0d816e6e7d7657a8559e9957d79dc1d77f
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Sat Mar 20 05:17:36 2021 -0700

    x86: Check cfun != NULL before accessing silent_p

    Since construct_container may be called with cfun == NULL, check
    cfun != NULL before accessing silent_p.

    gcc/

            PR target/99679
            * config/i386/i386.c (construct_container): Check cfun != NULL
            before accessing silent_p.

    gcc/testsuite/

            PR target/99679
            * g++.target/i386/pr99679-1.C: New test.
            * g++.target/i386/pr99679-2.C: Likewise.

  parent reply	other threads:[~2021-03-20 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20 10:07 [Bug target/99679] New: " marxin at gcc dot gnu.org
2021-03-20 10:07 ` [Bug target/99679] " marxin at gcc dot gnu.org
2021-03-20 17:12 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-20 17:12 ` hjl.tools at gmail dot com

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-99679-4-W43h1fE4c3@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).