public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/57051] Optimization regression in 4.8.0 from 4.7.2
Date: Fri, 17 May 2013 12:27:00 -0000	[thread overview]
Message-ID: <bug-57051-4-y3V74iS7l9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57051-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57051

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri May 17 08:31:32 2013
New Revision: 199002

URL: http://gcc.gnu.org/viewcvs?rev=199002&root=gcc&view=rev
Log:
    PR tree-optimization/57051
    * fold-const.c (const_binop) <case VEC_LSHIFT_EXPR,
    case VEC_RSHIFT_EXPR>: Fix BYTES_BIG_ENDIAN handling.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/fold-const.c

Author: jakub
Date: Fri May 17 08:52:36 2013
New Revision: 199004

URL: http://gcc.gnu.org/viewcvs?rev=199004&root=gcc&view=rev
Log:
    PR tree-optimization/57051
    * fold-const.c (const_binop) <case VEC_LSHIFT_EXPR,
    case VEC_RSHIFT_EXPR>: Fix BYTES_BIG_ENDIAN handling.

Modified:
    branches/gcc-4_8-branch/gcc/ChangeLog
    branches/gcc-4_8-branch/gcc/fold-const.c


      parent reply	other threads:[~2013-05-17 12:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 16:25 [Bug c/57051] New: " tony.howard-co84udjx at yopmail dot com
2013-04-24  8:10 ` [Bug tree-optimization/57051] " mpolacek at gcc dot gnu.org
2013-04-24  8:30 ` [Bug tree-optimization/57051] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2013-04-24 10:44 ` jakub at gcc dot gnu.org
2013-04-26 13:17 ` jakub at gcc dot gnu.org
2013-05-03 13:57 ` [Bug tree-optimization/57051] [4.8 " jakub at gcc dot gnu.org
2013-05-03 14:00 ` [Bug tree-optimization/57051] " jakub at gcc dot gnu.org
2013-05-06 11:55 ` rguenth at gcc dot gnu.org
2013-05-17 12:27 ` jakub at gcc dot gnu.org [this message]

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-57051-4-y3V74iS7l9@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).