This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Segment register support for the i386
- To: Joern Rennecke <amylaar at cygnus dot co dot uk>
- Subject: Re: Segment register support for the i386
- From: Denis Chertykov <denisc at overta dot ru>
- Date: 06 Jan 2000 22:47:44 +0300
- Cc: Denis Chertykov <denisc at overta dot ru>, Sergey Larin <larin at overta dot ru>, gcc at gcc dot gnu dot org
- References: <200001061925.TAA12299@phal.cygnus.co.uk>
Joern Rennecke <amylaar@cygnus.co.uk> writes:
> > >From this descriptions I can generate:
> ...
> > - LEGITIMIZE_RELOAD_ADDRESS;
>
> I don't see that you can generate LEGITIMIZE_RELOAD_ADDRESS.
I must write:
- part of LEGITIMIZE_RELOAD_ADDRESS;
I think about LEGITIMIZE_RELOAD_ADDRESS only for correct
BASE_REG_CLASS in reload pass.
Not all registers from BASE_REG_CLASS can be used as reg+offset.
but LEGITIMIZE_RELOAD_ADDRESS don't called in any case.
Also I must correct `find_reloads_address' to using
LEGITIMIZE_RELOAD_ADDRESS in any case, independent from `memrefloc'.
I must write:
- part of LEGITIMIZE_RELOAD_ADDRESS;
> You not only need to know the available offset ranges, but also
> how constants can be loaded and their cost.
>
> And you also neet to know when it is most useful to use an index
> register.
Yes. Yes.
LEGITIMIZE_RELOAD_ADDRESS always must exists.
Any suggestions ?
Denis.
PS: Are anybody really interesten in results of this work ?