This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [lto] implement awful types_compatible_p hack


Toon Moene wrote:
> Kenneth Zadeck wrote:
>
> > I wrote:
>
>>> Ahhhhhh ... Does that mean I can start writing my GCC Summit 2008
>>> paper: "Link Time Optimization: What's in it for Fortran ?"
>>>
>>> Thanks for all the great work you're doing on this branch !
>>>
>> unfortunately no
>>
>> we only do c at this point.
>>
>> and just between you and me, none of this is going to really help
>> fortran unless you can get real high level array operations into gimple
>> and we solve carrying the language specific aliasing info into lto.
>
> Ah, but I still can theorize about what the Link Time Optimization
> *could* do for Fortran.  That'd be the topic of my paper :-)
>
> How about "I do not agree with you about 'unless you can get real high
> level array operations into gimple '" ?
>
> See you in June !
>
toon,

I do not think that you should have had to do that stuff that you did in
the fortran front end.  We should be able to represent enough
information about fortran arrays and aliasing so that you do not need to
do that so early.

If we are able to do that, then lto would be able to do those same
transformation after doing a round of inter file inlining. 

kenny


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]