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 middle-end/103163] [12 Regression] stack_limit_rtx is created too early
Date: Wed, 17 Nov 2021 07:40:13 +0000 [thread overview]
Message-ID: <bug-103163-4-pTR7chj3fI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103163-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103163
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|stack_limit_rtx is created |[12 Regression]
|too early |stack_limit_rtx is created
| |too early
Target Milestone|--- |12.0
Ever confirmed|0 |1
Last reconfirmed| |2021-11-17
Status|UNCONFIRMED |NEW
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> Looks like the powerpc folks did report PR 101157 (right after
> r12-1702-g7232f7c4c2d727431096a) which was the failure of
> gcc.target/powerpc/pr48344-1.c but they reported it was fixed not far after
> the failure ...
But still fails:
https://gcc.gnu.org/pipermail/gcc-testresults/2021-November/735755.html
The ICE is new on the trunk though.
next prev parent reply other threads:[~2021-11-17 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 2:48 [Bug other/103163] New: " sandra at gcc dot gnu.org
2021-11-17 7:36 ` [Bug middle-end/103163] " pinskia at gcc dot gnu.org
2021-11-17 7:40 ` pinskia at gcc dot gnu.org [this message]
2021-11-17 7:40 ` [Bug middle-end/103163] [12 Regression] " pinskia at gcc dot gnu.org
2022-01-17 12:59 ` [Bug middle-end/103163] [12 Regression] stack_limit_rtx is created too early causing nregs field on REG to be zero (gcc.target/nios2/nios2-stack-check-1.c and gcc.target/powerpc/stack-limit.c) rguenth at gcc dot gnu.org
2022-01-17 17:37 ` pinskia at gcc dot gnu.org
2022-01-18 17:29 ` cvs-commit at gcc dot gnu.org
2022-01-18 17:32 ` sandra 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-103163-4-pTR7chj3fI@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).