On Thu, 28 Nov 2013, Jan Hubicka wrote:
> We previously renamed every static function foo into foo.1234 (just as a
> precaution because other compilation unit may have also function foo).
> This confuses many thins, so now we do renaming only when we see a
> conflict.
Ah, I see. Thanks.
>
> > + Functions are no longer pointlessly renamed.
>
> Readers may struggle a bit with this. What does it refer to?
We previously renamed every static function foo into foo.1234
(just as a precaution because other compilation unit may have also function
foo).
This confuses many thins, so n
On Mon, 18 Nov 2013, Jan Hubicka wrote:
> there was many changes in this area. The following are ones I can think
> of. Please fell free to suggest more changes. We probably should mention
> Teresa's splitting work once it is complete and new micro-architectures
> targetd by x86 backend.
Yes,
