public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56864] [4.9 regression] FAIL: gcc.dg/vect/costmodel/ppc/costmodel-vect-76b.c scan-tree-dump-times vect "vectorized 1 loops" 0
Date: Sun, 07 Apr 2013 17:33:00 -0000 [thread overview]
Message-ID: <bug-56864-4-wVzxFiKvUM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56864-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56864
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steven at gcc dot gnu.org
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2013-04-07 17:33:12 UTC ---
> Neither r196686 nor r197531 are revisions on the trunk.
Well, I record the revision number given by svn:
Updated to revision xxxxxx
The corresponding actual revision for trunk may be some number below, e.g.,
197530 for 197531, or 196683 for 196686. If you know a simple way to get the
last actual revision for trunk (branch), I'll be glad to use it.
Note that between r197531 and r197541, the only changes I can find are r197533
and r197534. Both are supposed to have been tested on
powerpc64-unknown-linux-gnu (see
http://gcc.gnu.org/ml/gcc-patches/2013-04/msg00263.html and
http://gcc.gnu.org/ml/gcc-patches/2013-04/msg00333.html), but may be not with
-m32. Since there is no division in the test, I suspect that if there is a
regression in the 197531 to 197541 range, it is likely r197533, hence CCed
Steven.
next prev parent reply other threads:[~2013-04-07 17:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 14:48 [Bug target/56864] New: " schwab@linux-m68k.org
2013-04-07 14:56 ` [Bug target/56864] " dominiq at lps dot ens.fr
2013-04-07 15:26 ` schwab@linux-m68k.org
2013-04-07 15:31 ` dominiq at lps dot ens.fr
2013-04-07 16:30 ` schwab@linux-m68k.org
2013-04-07 17:33 ` dominiq at lps dot ens.fr [this message]
2013-04-08 11:16 ` rguenth at gcc dot gnu.org
2013-05-01 17:49 ` wschmidt at gcc dot gnu.org
2013-05-01 20:07 ` schwab@linux-m68k.org
2013-05-01 20:13 ` wschmidt at gcc dot gnu.org
2013-05-02 10:37 ` schwab@linux-m68k.org
2013-05-02 15:55 ` wschmidt at gcc dot gnu.org
2013-05-02 16:20 ` schwab@linux-m68k.org
2013-05-02 16:36 ` schwab@linux-m68k.org
2013-07-23 17:36 ` dje at gcc dot gnu.org
2013-10-25 12:52 ` rguenth at gcc dot gnu.org
2013-10-25 13:20 ` 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-56864-4-wVzxFiKvUM@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).