public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61306] [4.10 Regression] wrong code at -Os and above on x86_64-linux-gnu
Date: Thu, 03 Jul 2014 21:45:00 -0000 [thread overview]
Message-ID: <bug-61306-4-Wtal6Sk9Db@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61306-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61306
Oleg Endo <olegendo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |olegendo at gcc dot gnu.org
--- Comment #10 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to thopre01 from comment #6)
> Author: thopre01
> Date: Wed Jun 11 10:04:33 2014
> New Revision: 211444
>
> URL: http://gcc.gnu.org/viewcvs?rev=211444&root=gcc&view=rev
> Log:
> 2014-06-11 Thomas Preud'homme <thomas.preudhomme@arm.com>
>
> gcc/
> PR tree-optimization/61306
> * tree-ssa-math-opts.c (struct symbolic_number): Store type of
> expression instead of its size.
> (do_shift_rotate): Adapt to change in struct symbolic_number. Return
> false to prevent optimization when the result is unpredictable due to
> arithmetic right shift of signed type with highest byte is set.
> (verify_symbolic_number_p): Adapt to change in struct symbolic_number.
> (init_symbolic_number): Likewise.
> (find_bswap_or_nop_1): Likewise. Return NULL to prevent optimization
> when the result is unpredictable due to sign extension.
>
> gcc/testsuite/
> * gcc.c-torture/execute/pr61306-1.c: New test.
> * gcc.c-torture/execute/pr61306-2.c: Likewise.
> * gcc.c-torture/execute/pr61306-3.c: Likewise.
>
> Added:
> trunk/gcc/testsuite/gcc.c-torture/execute/pr61306-1.c
> trunk/gcc/testsuite/gcc.c-torture/execute/pr61306-2.c
> trunk/gcc/testsuite/gcc.c-torture/execute/pr61306-3.c
> Modified:
> trunk/gcc/ChangeLog
> trunk/gcc/testsuite/ChangeLog
> trunk/gcc/tree-ssa-math-opts.c
It seems that after this commit, one SH bswap32 test started to fail.
Comparing the two test reports:
https://gcc.gnu.org/ml/gcc-testresults/2014-06/msg00961.html
https://gcc.gnu.org/ml/gcc-testresults/2014-06/msg01086.html
shows a new failure for gcc.target/sh/pr53568-1.c.
The function
int
test_func_02 (int a)
{
/* 1x swap.w
2x swap.b */
return (((a >> 0) & 0xFF) << 24)
| (((a >> 8) & 0xFF) << 16)
| (((a >> 16) & 0xFF) << 8)
| (((a >> 24) & 0xFF) << 0);
}
now fails to produce a bswap32.
next prev parent reply other threads:[~2014-07-03 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 2:58 [Bug tree-optimization/61306] New: " su at cs dot ucdavis.edu
2014-05-26 12:20 ` [Bug tree-optimization/61306] [4.10 Regression] " rguenth at gcc dot gnu.org
2014-05-26 12:22 ` rguenth at gcc dot gnu.org
2014-05-27 5:50 ` thomas.preudhomme at arm dot com
2014-05-28 11:47 ` thomas.preudhomme at arm dot com
2014-05-30 6:40 ` thomas.preudhomme at arm dot com
2014-06-11 10:05 ` thopre01 at gcc dot gnu.org
2014-06-11 10:06 ` thopre01 at gcc dot gnu.org
2014-06-30 1:59 ` thopre01 at gcc dot gnu.org
2014-06-30 2:12 ` thopre01 at gcc dot gnu.org
2014-07-03 21:45 ` olegendo at gcc dot gnu.org [this message]
2014-07-04 4:41 ` thopre01 at gcc dot gnu.org
2014-11-19 13:39 ` [Bug tree-optimization/61306] [5 " 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-61306-4-Wtal6Sk9Db@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).