From: Eric Botcazou <ebotcazou@adacore.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, i386]: Extend TARGET_READ_MODIFY{,_WRITE} peepholes to all integer modes
Date: Fri, 29 Apr 2016 10:17:00 -0000 [thread overview]
Message-ID: <3799415.uPfXC5v7Nr@polaris> (raw)
In-Reply-To: <CAFULd4bTG7k32mP2R-Fp4jPAzatUUexq8LFLrz4UhkSigr41Vw@mail.gmail.com>
> I'm testing the attached patch. Does it fix your ada failures?
No, it totally breaks stack checking. :-(
=== acats tests ===
FAIL: c52103x
FAIL: c52104x
+FAIL: c52104y
+FAIL: cb1010a
+FAIL: cb1010c
+FAIL: cb1010d
=== acats Summary ===
-# of expected passes 2318
-# of unexpected failures 2
+# of expected passes 2314
+# of unexpected failures 6
Native configuration is x86_64-suse-linux-gnu
=== gcc tests ===
@@ -133,11 +137,24 @@
Running target unix
+FAIL: gnat.dg/opt49.adb 3 blank line(s) in output
+FAIL: gnat.dg/opt49.adb (test for excess errors)
+UNRESOLVED: gnat.dg/opt49.adb compilation failed to produce executable
+FAIL: gnat.dg/stack_check1.adb 3 blank line(s) in output
+FAIL: gnat.dg/stack_check1.adb (test for excess errors)
+UNRESOLVED: gnat.dg/stack_check1.adb compilation failed to produce executable
+FAIL: gnat.dg/stack_check2.adb 3 blank line(s) in output
+FAIL: gnat.dg/stack_check2.adb (test for excess errors)
+UNRESOLVED: gnat.dg/stack_check2.adb compilation failed to produce executable
+FAIL: gnat.dg/stack_check3.adb 3 blank line(s) in output
+FAIL: gnat.dg/stack_check3.adb (test for excess errors)
/home/eric/svn/gcc/gcc/testsuite/gnat.dg/opt49.adb:31:4: error: unrecognizable
insn:
(insn 33 32 34 8 (parallel [
(set (mem/v:DI (reg/f:DI 7 sp) [0 S8 A8])
(unspec [
(const_int 0 [0])
] UNSPEC_PROBE_STACK))
(clobber (reg:CC 17 flags))
]) /home/eric/svn/gcc/gcc/testsuite/gnat.dg/opt49.adb:17 -1
(nil))
+===========================GNAT BUG DETECTED==============================+
| 7.0.0 20160429 (experimental) [trunk revision 235619] (x86_64-suse-linux)
GCC error:|
| in extract_insn, at recog.c:2287 |
| Error detected around
/home/eric/svn/gcc/gcc/testsuite/gnat.dg/opt49.adb:31:4|
--
Eric Botcazou
next prev parent reply other threads:[~2016-04-29 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 19:16 Uros Bizjak
2016-04-29 7:47 ` Eric Botcazou
2016-04-29 7:50 ` Uros Bizjak
2016-04-29 7:58 ` Eric Botcazou
2016-04-29 9:30 ` Uros Bizjak
2016-04-29 10:17 ` Eric Botcazou [this message]
2016-04-29 10:51 ` Uros Bizjak
2016-04-29 11:23 ` Eric Botcazou
2016-04-29 11:52 ` Uros Bizjak
2016-04-29 14:30 ` Eric Botcazou
2016-04-29 14:44 ` Uros Bizjak
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=3799415.uPfXC5v7Nr@polaris \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ubizjak@gmail.com \
/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).