public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/19121] [4.0 Regression] ICE: in merge_alias_info, at tree-ssa-copy.c:236
Date: Tue, 18 Jan 2005 03:54:00 -0000 [thread overview]
Message-ID: <20050118035442.27067.qmail@sourceware.org> (raw)
In-Reply-To: <20041221220253.19121.v.haisman@sh.cvut.cz>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-01-18 03:54 -------
Subject: Bug 19121
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: dnovillo@gcc.gnu.org 2005-01-18 03:54:38
Modified files:
gcc : ChangeLog tree-ssa-alias.c tree-ssa-copy.c
tree-ssa.c
gcc/testsuite : ChangeLog
Added files:
gcc/testsuite/gcc.c-torture/compile: pr19121.c
Log message:
PR tree-optimization/19121
* tree-ssa-alias.c (compute_flow_sensitive_aliasing): When
adding aliases to a name tag, also add them to the pointer's
type tag.
* tree-ssa-copy.c (merge_alias_info): Do not merge flow
sensitive alias info at all. Only check that the two pointers
have compatible pointed-to sets.
* tree-ssa.c (verify_name_tags): Verify that the alias set of
a pointer's type tag is a superset of the alias set of the
pointer's name tag.
testsuite/ChangeLog:
PR tree-optimization/19121
* gcc.c-torture/compile/pr19121.c: New test.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.7163&r2=2.7164
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-ssa-alias.c.diff?cvsroot=gcc&r1=2.65&r2=2.66
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-ssa-copy.c.diff?cvsroot=gcc&r1=2.21&r2=2.22
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-ssa.c.diff?cvsroot=gcc&r1=2.70&r2=2.71
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.4899&r2=1.4900
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gcc.c-torture/compile/pr19121.c.diff?cvsroot=gcc&r1=NONE&r2=1.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19121
prev parent reply other threads:[~2005-01-18 3:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 22:03 [Bug c/19121] New: " v dot haisman at sh dot cvut dot cz
2004-12-21 22:03 ` [Bug c/19121] " v dot haisman at sh dot cvut dot cz
2004-12-21 22:10 ` [Bug tree-optimization/19121] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-12-21 22:12 ` pinskia at gcc dot gnu dot org
2004-12-21 23:25 ` pinskia at gcc dot gnu dot org
2004-12-21 23:27 ` pinskia at gcc dot gnu dot org
2004-12-21 23:41 ` pinskia at gcc dot gnu dot org
2004-12-22 2:25 ` pinskia at gcc dot gnu dot org
2004-12-22 2:27 ` pinskia at gcc dot gnu dot org
2004-12-22 2:35 ` pinskia at gcc dot gnu dot org
2004-12-22 23:13 ` pinskia at gcc dot gnu dot org
2004-12-23 5:56 ` pinskia at gcc dot gnu dot org
2004-12-23 6:21 ` pinskia at gcc dot gnu dot org
2004-12-23 20:33 ` pinskia at gcc dot gnu dot org
2005-01-07 15:14 ` dnovillo at gcc dot gnu dot org
2005-01-18 3:53 ` dnovillo at gcc dot gnu dot org
2005-01-18 3:54 ` cvs-commit 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=20050118035442.27067.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).