public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/60429] [4.7 Regression] Miscompilation (aliasing) with -finline-functions
Date: Mon, 24 Mar 2014 08:43:00 -0000 [thread overview]
Message-ID: <bug-60429-4-z8M5bXV797@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60429-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60429
--- Comment #31 from rguenther at suse dot de <rguenther at suse dot de> ---
On Sat, 22 Mar 2014, mikpelinux at gmail dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60429
>
> Mikael Pettersson <mikpelinux at gmail dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |mikpelinux at gmail dot com
>
> --- Comment #29 from Mikael Pettersson <mikpelinux at gmail dot com> ---
> Richard, your 4.8 backport performs the same call twice in a row on lines 3017
> and 3018 in tree-ssa-structalias.c; is that really intentional?
>
> + /* We have to include all fields that overlap the current
> + field shifted by rhsoffset. And we include at least
> + the last or the first field of the variable to represent
> + reachability of off-bound addresses, in particular &object + 1,
> + conservatively correct. */
> + temp = first_or_preceding_vi_for_offset (curr, offset);
> + temp = first_or_preceding_vi_for_offset (curr, offset);
No, fixed.
next prev parent reply other threads:[~2014-03-24 8:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 13:12 [Bug libgcc/60429] New: " linux at carewolf dot com
2014-03-05 13:13 ` [Bug libgcc/60429] " linux at carewolf dot com
2014-03-05 13:17 ` linux at carewolf dot com
2014-03-05 13:28 ` linux at carewolf dot com
2014-03-05 13:29 ` linux at carewolf dot com
2014-03-06 10:10 ` [Bug middle-end/60429] " rguenth at gcc dot gnu.org
2014-03-06 19:07 ` linux at carewolf dot com
2014-03-07 12:18 ` rguenth at gcc dot gnu.org
2014-03-07 16:36 ` linux at carewolf dot com
2014-03-07 16:38 ` linux at carewolf dot com
2014-03-07 16:38 ` linux at carewolf dot com
2014-03-07 16:44 ` linux at carewolf dot com
2014-03-07 18:47 ` pinskia at gcc dot gnu.org
2014-03-07 19:58 ` linux at carewolf dot com
2014-03-07 20:02 ` trippels at gcc dot gnu.org
2014-03-07 20:26 ` trippels at gcc dot gnu.org
2014-03-07 21:40 ` [Bug middle-end/60429] [4.7/4.8/4.9 Regression] " jakub at gcc dot gnu.org
2014-03-10 9:05 ` rguenth at gcc dot gnu.org
2014-03-10 10:42 ` rguenth at gcc dot gnu.org
2014-03-10 11:29 ` rguenth at gcc dot gnu.org
2014-03-10 13:18 ` rguenth at gcc dot gnu.org
2014-03-11 12:42 ` rguenth at gcc dot gnu.org
2014-03-11 12:59 ` [Bug middle-end/60429] [4.7/4.8 " rguenth at gcc dot gnu.org
2014-03-11 14:38 ` linux at carewolf dot com
2014-03-15 13:20 ` linux at carewolf dot com
2014-03-17 8:30 ` rguenther at suse dot de
2014-03-17 13:09 ` rguenth at gcc dot gnu.org
2014-03-17 13:09 ` [Bug middle-end/60429] [4.7 " rguenth at gcc dot gnu.org
2014-03-24 8:43 ` rguenth at gcc dot gnu.org
2014-03-24 8:43 ` rguenth at gcc dot gnu.org [this message]
2014-06-12 13:37 ` 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-60429-4-z8M5bXV797@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).