Undefined behavior in genautomata.c?
Daniel Berlin
dberlin@dberlin.org
Mon Sep 19 14:05:00 GMT 2005
>> 1. Not interprocedurally.
>
> True, it was written before the IPA infrastructure was added.
> For 4.2 the plan is to rewrite it using Diego's propagator and then
> IPA propagation should be added too. It will be useful for both
> __builtin_object_size builtin itself as well as other passes that might
> use the info (e.g. mudflap).
Yes, that was what i was planning to do, but if you are going to do it,
i'll leave it to you because i have about 2000 other things to do.
:)
It should stash the info somewhere, possibly
SSA_NAME_PTR_INFO->max_allocated_size
(i know it can compute min, etc, but for estimating iteration counts, we
have to use MAX).
>
>> 2. Not for regular objects, only things involved with
>> builtin_object_siz.
>
> Not true, you can call it internally on any anything.
Right, just as soon as you look up what bits you need to pass it from
the builtin_object_size docs :)
(Yes yes, i know, easily solvable :P)
More information about the Gcc
mailing list