This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: SH: use register names instead of numbers
- To: Joern Rennecke <amylaar at redhat dot com>
- Subject: Re: SH: use register names instead of numbers
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 22 Nov 2000 18:44:42 -0200
- Cc: rth at redhat dot com (Richard Henderson), zackw at Stanford dot EDU (Zack Weinberg), gcc-patches at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <200011222007.eAMK7v403301@tantra.cygnus.co.uk><orhf4z4v7h.fsf@guarana.lsd.ic.unicamp.br>
On Nov 22, 2000, Alexandre Oliva <aoliva@redhat.com> wrote:
> On Nov 22, 2000, Joern Rennecke <amylaar@redhat.com> wrote:
>>> But what if I want to refer to the constants #defined in insn-codes.h
>>> in machine-specific header files? There are at least half a dozen C
>>> sources that currently fall victim of this problem in the new set-up.
>>> Should I just add insn-codes.h to the list of machine-specific headers
>>> (which might result in some cyclic dependency), or can someone come up
>> Is there indeed a cyclic dependency?
>> I thought that insn-codes.h is built without needing tm.h ?
> There appears to be. Most xm-*.h include tm.h.
> Houston, we have a problem :-)
Ok, copying the constants from insn-codes.h to insn-config.h covers
most of the programs that had failed to compile, and insn-config.h
even makes sense for constants. But resource.c and rtlanal.c still
won't compile unless I explicitly #include "insn-config.h". Does this
sound reasonable?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me