public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96072] [10/11/12 Regression] ICE: Segmentation fault (in add_reg_note)
Date: Thu, 15 Sep 2022 05:44:04 +0000 [thread overview]
Message-ID: <bug-96072-4-y73sheCryK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96072-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96072
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gnu.org
Status|NEW |ASSIGNED
Summary|ICE: Segmentation fault (in |[10/11/12 Regression] ICE:
|add_reg_note) |Segmentation fault (in
| |add_reg_note)
--- Comment #7 from Kewen Lin <linkw at gcc dot gnu.org> ---
I confirmed this is one regression, it passed with r10-7980 but started to fail
with r10-7981. And it's reproducible on ppc64 be machine with options "-m32
-O1".
next prev parent reply other threads:[~2022-09-15 5:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 4:47 [Bug target/96072] New: " asolokha at gmx dot com
2020-08-11 4:13 ` [Bug target/96072] " asolokha at gmx dot com
2020-08-19 7:30 ` asolokha at gmx dot com
2022-09-13 22:25 ` segher at gcc dot gnu.org
2022-09-14 2:33 ` asolokha at gmx dot com
2022-09-14 12:20 ` linkw at gcc dot gnu.org
2022-09-14 12:23 ` linkw at gcc dot gnu.org
2022-09-15 5:44 ` linkw at gcc dot gnu.org [this message]
2022-09-26 5:34 ` [Bug target/96072] [10/11/12 Regression] " cvs-commit at gcc dot gnu.org
2022-10-19 9:05 ` cvs-commit at gcc dot gnu.org
2022-10-19 11:24 ` cvs-commit at gcc dot gnu.org
2022-10-20 2:16 ` cvs-commit at gcc dot gnu.org
2022-10-20 2:28 ` linkw 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-96072-4-y73sheCryK@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).