On 10/29/13 04:40, Richard Biener wrote:
Of course in the example we have the "global memory" storage class
(incoming function argument) and "malloc memory" which is really
the same storage class. It only becomes a different storage class
if you factor in flow analysis (for which the current PTA code is weak
once you leave the SSA web).
The global memory storage class is really better thought of as "i
haven't a clue" class.
You want a different class for things passed in as you know they can't
conflict with anything in the current function's stack or anything
malloc'd by the current function.
Jeff
