public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63256] New: [5.0 regression] FAIL: gcc.dg/sms-8.c scan-rtl-dump-times sms "SMS succeeded" 0
Date: Sat, 13 Sep 2014 13:20:00 -0000 [thread overview]
Message-ID: <bug-63256-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63256
Bug ID: 63256
Summary: [5.0 regression] FAIL: gcc.dg/sms-8.c
scan-rtl-dump-times sms "SMS succeeded" 0
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: schwab@linux-m68k.org
CC: segher at kernel dot crashing.org
Target: powerpc-*-*
Only happens with -m32.
$ gcc/xgcc -Bgcc/ ../gcc/gcc/testsuite/gcc.dg/sms-8.c
-fno-diagnostics-show-caret -fdiagnostics-color=never -O2 -fmodulo-sched
-fmodulo-sched-allow-regmoves -fdump-rtl-sms -ffat-lto-objects -lm -m32 -o
./sms-8.exe
$ grep "SMS succeeded" sms-8.c.214r.sms
../gcc/gcc/testsuite/gcc.dg/sms-8.c:18 SMS succeeded 12 2 (with ii, sc)
96f3c2b9903e92cf806719d18fc0682d617c0016 is the first bad commit
commit 96f3c2b9903e92cf806719d18fc0682d617c0016
Author: segher <segher@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Tue Sep 2 11:21:09 2014 +0000
2014-09-02 Segher Boessenkool <segher@kernel.crashing.org>
* config/rs6000/rs6000.md (any_extend): New code iterator.
(u, su): New code attributes.
(dmode, DMODE): New mode attributes.
(<su>mul<mode>3_highpart): New.
(*<su>mul<mode>3_highpart): New.
(<su>mulsi3_highpart_le): New.
(<su>muldi3_highpart_le): New.
(<su>mulsi3_highpart_64): New.
(<u>mul<mode><dmode>3): New.
(mulsidi3, umulsidi3, smulsi3_highpart, umulsi3_highpart, and two
splitters): Delete.
(mulditi3, umulditi3, smuldi3_highpart, umuldi3_highpart, and two
splitters): Delete.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@214814
138bc75d-0d04-0410-961f-82ee72b054a4
next reply other threads:[~2014-09-13 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 13:20 schwab@linux-m68k.org [this message]
2014-09-13 21:36 ` [Bug target/63256] " segher at gcc dot gnu.org
2014-09-15 9:04 ` rguenth at gcc dot gnu.org
2014-11-24 13:19 ` [Bug testsuite/63256] [5 " rguenth at gcc dot gnu.org
2015-02-03 3:51 ` segher at gcc dot gnu.org
2015-02-09 20:47 ` segher at gcc dot gnu.org
2015-02-25 0:23 ` segher at gcc dot gnu.org
2015-03-25 9:04 ` segher at gcc dot gnu.org
2015-04-22 12:02 ` [Bug testsuite/63256] [5/6 " jakub at gcc dot gnu.org
2015-07-16 9:15 ` rguenth 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-63256-4@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).