public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44406] wrong code generation with -ftree-sra
Date: Mon, 07 Jun 2010 16:51:00 -0000 [thread overview]
Message-ID: <20100607165125.19788.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44406-19278@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from jamborm at gcc dot gnu dot org 2010-06-07 16:51 -------
Moreover, I cannot reproduce this bug on the 4.5 branch since:
r159866 | rguenth | 2010-05-26 13:46:01 +0200 (Wed, 26 May 2010) | 12 lines
2010-05-26 Richard Guenther <rguenther@suse.de>
PR rtl-optimization/44164
* tree-ssa-alias.c (aliasing_component_refs_p): Fix the
no-common access-path disambiguation.
(indirect_ref_may_alias_decl_p): Adjust.
(indirect_refs_may_alias_p): Likewise.
(refs_may_alias_p_1): Likewise.
* gcc.c-torture/execute/pr44164.c: New testcase.
* g++.dg/tree-ssa/pr13146.C: Adjust.
So, I think it is the same bug and mark it accordingly.
*** This bug has been marked as a duplicate of 44164 ***
--
jamborm at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |DUPLICATE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44406
prev parent reply other threads:[~2010-06-07 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 19:07 [Bug c++/44406] New: " torbenh at users dot sourceforge dot net
2010-06-03 19:08 ` [Bug c++/44406] " torbenh at users dot sourceforge dot net
2010-06-03 19:11 ` torbenh at users dot sourceforge dot net
2010-06-04 16:43 ` [Bug tree-optimization/44406] " jamborm at gcc dot gnu dot org
2010-06-07 16:51 ` jamborm at gcc dot gnu dot 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=20100607165125.19788.qmail@sourceware.org \
--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).