public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/43879] -fipa-pta causes various miscompilations
Date: Tue, 04 May 2010 13:13:00 -0000 [thread overview]
Message-ID: <20100504131242.798.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43879-14164@http.gcc.gnu.org/bugzilla/>
------- Comment #30 from rguenth at gcc dot gnu dot org 2010-05-04 13:12 -------
Subject: Bug 43879
Author: rguenth
Date: Tue May 4 13:12:02 2010
New Revision: 159026
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159026
Log:
2010-05-04 Richard Guenther <rguenther@suse.de>
PR tree-optimization/43879
* tree-ssa-structalias.c (alias_get_name): Use
DECL_ASSEMBLER_NAME if available.
(create_function_info_for): Return the varinfo node.
(ipa_pta_execute): Associate same-body aliases and extra names
with their origin nodes varinfo. Dump DECL_ASSEMBLER_NAME.
* g++.dg/torture/pr43879-1_0.C: New testcase.
* g++.dg/torture/pr43879-1_1.C: Likewise.
Added:
trunk/gcc/testsuite/g++.dg/torture/pr43879-1_0.C
trunk/gcc/testsuite/g++.dg/torture/pr43879-1_1.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-structalias.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43879
next prev parent reply other threads:[~2010-05-04 13:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 15:54 [Bug tree-optimization/43879] New: [4.6 Regression] -fipa-pta causes FAIL: gcc.c-torture/execute/20000822-1.c execution zsojka at seznam dot cz
2010-04-24 16:18 ` [Bug tree-optimization/43879] " zsojka at seznam dot cz
2010-04-24 18:49 ` [Bug tree-optimization/43879] [4.6 Regression] -fipa-pta causes various miscompilations zsojka at seznam dot cz
2010-04-24 18:55 ` [Bug tree-optimization/43879] " rguenth at gcc dot gnu dot org
2010-04-24 20:04 ` rguenth at gcc dot gnu dot org
2010-04-28 11:52 ` rguenth at gcc dot gnu dot org
2010-04-28 12:53 ` rguenth at gcc dot gnu dot org
2010-04-28 15:09 ` zsojka at seznam dot cz
2010-04-28 15:13 ` zsojka at seznam dot cz
2010-04-29 15:30 ` rguenth at gcc dot gnu dot org
2010-04-29 15:37 ` rguenth at gcc dot gnu dot org
2010-04-30 8:23 ` rguenth at gcc dot gnu dot org
2010-04-30 9:32 ` rguenth at gcc dot gnu dot org
2010-04-30 10:06 ` rguenth at gcc dot gnu dot org
2010-04-30 13:57 ` rguenth at gcc dot gnu dot org
2010-04-30 14:51 ` dominiq at lps dot ens dot fr
2010-04-30 15:17 ` rguenth at gcc dot gnu dot org
2010-04-30 15:27 ` jv244 at cam dot ac dot uk
2010-04-30 15:53 ` dominiq at lps dot ens dot fr
2010-04-30 17:13 ` rguenth at gcc dot gnu dot org
2010-04-30 18:54 ` rguenth at gcc dot gnu dot org
2010-05-02 13:45 ` zsojka at seznam dot cz
2010-05-02 13:47 ` zsojka at seznam dot cz
2010-05-02 18:11 ` rguenth at gcc dot gnu dot org
2010-05-02 18:12 ` rguenth at gcc dot gnu dot org
2010-05-03 14:56 ` zsojka at seznam dot cz
2010-05-03 15:02 ` zsojka at seznam dot cz
2010-05-03 16:56 ` steven at gcc dot gnu dot org
2010-05-03 23:46 ` zsojka at seznam dot cz
2010-05-04 11:16 ` rguenth at gcc dot gnu dot org
2010-05-04 13:13 ` rguenth at gcc dot gnu dot org [this message]
2010-05-04 14:02 ` rguenth at gcc dot gnu dot 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=20100504131242.798.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).