[Bug tree-optimization/2462] "restrict" implementation bug
dann at godzilla dot ics dot uci dot edu
gcc-bugzilla@gcc.gnu.org
Thu Jun 25 15:31:00 GMT 2009
------- Comment #8 from dann at godzilla dot ics dot uci dot edu 2009-06-25 15:31 -------
(In reply to comment #7)
> 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).
The intention for link_error was to just make it easier to write a test, not to
prohibit optimization.
Please feel free to adjust the code accordingly.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2462
More information about the Gcc-bugs
mailing list