This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: more on PR3179 (fortran and some target backends)
- To: Joel Sherrill <joel at OARcorp dot com>
- Subject: Re: more on PR3179 (fortran and some target backends)
- From: "Zack Weinberg" <zackw at stanford dot edu>
- Date: Wed, 20 Jun 2001 01:16:59 -0700
- Cc: gcc-bugs at gcc dot gnu dot org, rth at redhat dot com, toon at moene dot indiv dot nluug dot nl
On Tue, Jun 19, 2001 at 05:08:59PM -0500, Joel Sherrill wrote:
> Sorry for following up so quickly but I have found the underlying cause
> and it is broader than the i960 and fortran.
>
> This problem is not specific to the i960 and may not be fortran
> specific. Some backends use c_lex.
>
> $ find . -type f | xargs -e grep -l c_lex
> ./gcc-3.0-20010614/gcc/config/c4x/c4x.c
> ./gcc-3.0-20010614/gcc/config/c4x/c4x.h
> ./gcc-3.0-20010614/gcc/config/i370/i370.c
> ./gcc-3.0-20010614/gcc/config/i960/i960.c
> ./gcc-3.0-20010614/gcc/config/v850/v850-c.c
c4x, i370, and i960 need to have the offending routines split out to
<target>-c.c files, as was already done for v850.
I can do it but it's probably better if the port maintainers do, I
can't test any of those platforms.
zw