This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PR 28152 Diagnostic about wrong use _Complex prints __complex__
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Manuel López-Ibáñez <lopezibanez at gmail dot com>
- Cc: Gcc Patch List <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 12 Aug 2008 14:29:38 +0000 (UTC)
- Subject: Re: PR 28152 Diagnostic about wrong use _Complex prints __complex__
- References: <6c33472e0808081009i134b7b58ief690f31ae383bf@mail.gmail.com>
On Fri, 8 Aug 2008, Manuel López-Ibáñez wrote:
> I don't understand why we would like to use the canonical name instead
> of whatever was parsed. Fixed by not doing this.
>
> Bootstrapped and regression tested on x86_64-pc-linux-gnu with
> --enable-languages=all.
>
> OK for trunk?
>
> 2008-08-08 Manuel Lopez-Ibanez <manu@gcc.gnu.org>
>
> PR c/28152
> * c-parser.c (c_lex_one_token): Do not store the canonical spelling
> for keywords.
> testsuite/
> * gcc.dg/parser-pr28152.c: New.
This is OK if you also add a test that __complex__ is used if that
spelling is used in the source. If the issue applies for C++ make sure
there's a PR open for that as well.
--
Joseph S. Myers
joseph@codesourcery.com