This is the mail archive of the gcc-bugs@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: PATCH: Re: ICE in 920624-1.c with -O3 -funroll-loops on vax-dec-ultrix4.3


> On Tue, Feb 05, 2002 at 01:40:50PM +0100, Jan Hubicka wrote:
> > Perhaps using symbol_ref is just fine. For calls we also do use
> > symbol refs to addresses inside code segment.
> 
> And on thouse troublesome ports we have ENCODE_SECTION_INFO
> to set e.g. SYMBOL_REF_FLAG to indicate a code segment address.
> >From whence would you call ENCODE_SECTION_INFO from this?
> 
> Of course, don't get me started on how SYMBOL_REF should be
> cleaned up as well.

Perhaps instead of generating many *_REF beasts, we should use
one with flags specifying the segment _REF is in. We partly do that
for SYMBOL_REF and static storage anyway.

But this is another involved topic :(

Honza
> 
> 
> r~


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