This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: driver/9822: The "%c" spec option produces: gcc: spec failure: unrecognized spec option 'c'
- From: Neil Booth <neil at daikokuya dot co dot uk>
- To: bradley-gnu at bradley dot lcs dot mit dot edu
- Cc: gcc-gnats at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org
- Date: Mon, 24 Feb 2003 07:02:51 +0000
- Subject: Re: driver/9822: The "%c" spec option produces: gcc: spec failure: unrecognized spec option 'c'
- References: <20030224062723.994.qmail@sources.redhat.com>
bradley-gnu at bradley dot lcs dot mit dot edu wrote:-
> I tried to write a spec file that used the %c option, but it is no longer accepted by the driver. The error is printed by line 5234 of gcc.c.
It's been removed as it is not necessary.
> The gcc.info documentation says that %c is accepted, however:
> > `%c'
> > Process the `signed_char' spec. This is intended to be used to
> > tell cpp whether a char is signed. It typically has the
> > definition:
> > %{funsigned-char:-D__CHAR_UNSIGNED__}
>
> This is probably a documentation bug, rather than a code bug.
I think so.
> The documentation on the spec files seems quite out-of-date.
> For example, I cannot figure out, from the documentation, what does this entry mean in the spec file.
> %{fsigned-char&unsigned-char}
That's documented in gcc.c. I'm not sure why SPECS have been
documented, they're really an internal thing in a constant state of
flux.
-fsigned-char or -funsigned-char should be all you need.
Neil.