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 middle-end/64065] [5 Regression] CP2K miscompilation at -O3 -flto
Date: Tue, 25 Nov 2014 13:23:00 -0000 [thread overview]
Message-ID: <bug-64065-4-bn24poCjvr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64065-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64065
--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 25 Nov 2014, Joost.VandeVondele at mat dot ethz.ch wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64065
>
> Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |Joost.VandeVondele at mat dot ethz
> | |.ch
>
> --- Comment #2 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
> (In reply to Richard Biener from comment #1)
> > That would be nice. Looking at the changes its either a latent issue
> > uncovered by inlining changes, my restrict change or my SCCVN change (which
> > might uncover a frontend bug - it did that for Java already).
>
> r218005: Fail
> r218004: OK
>
> Which makes it restrict changes, I guess.
:/
Might make it a bad interaction with the "special" support we have
for the Fortran frontend or a genuine bug. Not sure without
something more self-contained. But at least I'll think a bit more
about the LTO side of that change. Ah! A bug.
next prev parent reply other threads:[~2014-11-25 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 7:23 [Bug middle-end/64065] New: " Joost.VandeVondele at mat dot ethz.ch
2014-11-25 9:18 ` [Bug middle-end/64065] " rguenth at gcc dot gnu.org
2014-11-25 13:08 ` Joost.VandeVondele at mat dot ethz.ch
2014-11-25 13:23 ` rguenther at suse dot de [this message]
2014-11-25 13:28 ` rguenth at gcc dot gnu.org
2014-11-25 15:14 ` Joost.VandeVondele at mat dot ethz.ch
2014-11-25 15:20 ` rguenther at suse dot de
2014-11-25 15:40 ` Joost.VandeVondele at mat dot ethz.ch
2014-11-25 16:43 ` rguenth at gcc dot gnu.org
2014-11-25 16:43 ` 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-64065-4-bn24poCjvr@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).