This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/2462] "restrict" implementation bug
- From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Jun 2009 10:28:20 -0000
- Subject: [Bug tree-optimization/2462] "restrict" implementation bug
- References: <bug-2462-1008@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from rguenth at gcc dot gnu dot org 2009-06-25 10:28 -------
With the new restrict implementation baz() works and all the rest would work
as well if the calls to link_error () would not cause the malloced memory
to be clobbered. The artifact here is that malloced memory is considered
global (we are not allowed to remove stores to it).
But this is all unrelated to restrict support which should be properly
fixed now.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2462