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 debug/51471] [4.7 Regression] gcc.c-torture/execute/20040811-1.c and gcc.c-torture/execute/vla-dealloc-1.c fails at -O3 -g on mips64-linux-gnu
Date: Wed, 14 Dec 2011 23:09:00 -0000 [thread overview]
Message-ID: <bug-51471-4-KmjhJZkOJt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51471-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51471
--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-12-14 22:58:55 UTC ---
This is the patch which I am testing:
Index: genattrtab.c
===================================================================
--- genattrtab.c (revision 182342)
+++ genattrtab.c (working copy)
@@ -4280,6 +4280,11 @@ write_eligible_delay (const char *kind)
printf (" if (!INSN_P (candidate_insn))\n");
printf (" return 0;\n");
printf ("\n");
+ /* Frame related instructions are hard to put in the delay slot for
+ debugging info reasons. */
+ printf (" if (RTX_FRAME_RELATED_P (candidate_insn))\n");
+ printf (" return 0;\n");
+ printf ("\n");
/* If more than one delay type, find out which type the delay insn is. */
next prev parent reply other threads:[~2011-12-14 22:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 19:50 [Bug debug/51471] New: " pinskia at gcc dot gnu.org
2011-12-08 19:51 ` [Bug debug/51471] [4.7 Regression] " pinskia at gcc dot gnu.org
2011-12-08 19:54 ` pinskia at gcc dot gnu.org
2011-12-10 0:02 ` pinskia at gcc dot gnu.org
2011-12-10 3:18 ` pinskia at gcc dot gnu.org
2011-12-12 12:48 ` vries at gcc dot gnu.org
2011-12-12 13:12 ` mikpe at it dot uu.se
2011-12-14 17:27 ` vries at gcc dot gnu.org
2011-12-14 18:19 ` jakub at gcc dot gnu.org
2011-12-14 20:28 ` pinskia at gcc dot gnu.org
2011-12-14 20:29 ` pinskia at gcc dot gnu.org
2011-12-14 23:09 ` pinskia at gcc dot gnu.org [this message]
2011-12-16 20:12 ` pinskia at gcc dot gnu.org
2011-12-19 13:35 ` vries at gcc dot gnu.org
2012-01-04 13:40 ` rguenth at gcc dot gnu.org
2012-01-04 20:01 ` pinskia at gcc dot gnu.org
2012-01-04 21:43 ` vries at gcc dot gnu.org
2012-01-04 22:25 ` pinskia at gcc dot gnu.org
2012-01-08 14:13 ` vries at gcc dot gnu.org
2012-01-10 8:50 ` vries at gcc dot gnu.org
2012-01-10 8:55 ` vries 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-51471-4-KmjhJZkOJt@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).