public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/59354] [4.8/4.9/5 Regression] Element swizzling produces invalid result with -O3
Date: Wed, 14 Jan 2015 09:47:00 -0000	[thread overview]
Message-ID: <bug-59354-4-ToJRfztIeu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59354-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59354

--- Comment #11 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 14 Jan 2015, ville.voutilainen at gmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59354
> 
> --- Comment #10 from Ville Voutilainen <ville.voutilainen at gmail dot com> ---
> (In reply to Jakub Jelinek from comment #9)
> > I can reproduce it even with r219580.
> 
> Likewise. People, remember to use -O3 when reproducing.

Will try in a non-dev tree then (and then identify which of the gazillion
local changes I have "fixes" it...)


  parent reply	other threads:[~2015-01-14  9:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 14:25 [Bug c++/59354] New: Unexpected result in g++ when casting int to char from an stl vector to an array jori.liesenborgs at gmail dot com
2015-01-01 13:54 ` [Bug c++/59354] " gcc-bugzilla at contacts dot eelis.net
2015-01-07 20:30 ` [Bug middle-end/59354] " ville.voutilainen at gmail dot com
2015-01-08 11:04 ` [Bug tree-optimization/59354] Element swizzling produces invalid result with -O3 (tree-cunrolli pass problem?) ubizjak at gmail dot com
2015-01-08 14:52 ` [Bug tree-optimization/59354] [4.8/4.9/5/Regression] " hjl.tools at gmail dot com
2015-01-08 14:54 ` jakub at gcc dot gnu.org
2015-01-08 14:59 ` hjl.tools at gmail dot com
2015-01-14  7:02 ` [Bug tree-optimization/59354] [4.8/4.9/5/Regression] Element swizzling produces invalid result with -O3 ubizjak at gmail dot com
2015-01-14  8:52 ` [Bug tree-optimization/59354] [4.8/4.9/5 Regression] " rguenth at gcc dot gnu.org
2015-01-14  8:57 ` jakub at gcc dot gnu.org
2015-01-14  8:59 ` ville.voutilainen at gmail dot com
2015-01-14  9:47 ` rguenther at suse dot de [this message]
2015-01-14 14:06 ` rguenth at gcc dot gnu.org
2015-01-14 14:09 ` [Bug tree-optimization/59354] [4.8/4.9 " rguenth at gcc dot gnu.org
2015-02-23 12:19 ` rguenth at gcc dot gnu.org
2015-06-23  8:46 ` [Bug tree-optimization/59354] [4.8 " 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-59354-4-ToJRfztIeu@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).