--- Comment #5 from rguenth at gcc dot gnu dot org 2009-04-03 11:16 ---
Subject: Bug 34743
Author: rguenth
Date: Fri Apr 3 11:16:29 2009
New Revision: 145497
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145497
Log:
2009-04-03 Richard Guenther
PR tree-optimization/
--- Comment #6 from rguenth at gcc dot gnu dot org 2009-04-03 11:16 ---
Fixed for 4.5.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
Status|N
--- Comment #4 from rguenth at gcc dot gnu dot org 2008-01-14 10:58 ---
Created an attachment (id=14940)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14940&action=view)
patch I was toying with
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34743
--- Comment #3 from rguenth at gcc dot gnu dot org 2008-01-14 10:56 ---
Let's defer this to stage1.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from rguenth at gcc dot gnu dot org 2008-01-11 16:39 ---
We even mark all pointed-to vars of value-escaping pointers as call-clobbered.
So I believe NMTs itself need never be call-clobbered. But there's also
hints that we cover bugs somewhere:
FIXME: This is no
--- Comment #1 from rguenth at gcc dot gnu dot org 2008-01-11 15:57 ---
It's doing the correct thing. We have
p_1, name memory tag: NMT.14, is dereferenced, points-to vars: { SFT.3 SFT.7 }
(SFT.3 is x.x, SFT.7 is z.x)
Now, NMT.14 is marked call clobbered:
NMT.14, UID D.1582, struct
