This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gcc cannot recognize "0xe+0x1"

From: Andreas Schwab <schwab at linux-m68k dot org>
To: kovaltan at gmail dot com
Cc: gcc-bugs at gcc dot gnu dot org
Date: Mon, 02 Mar 2009 10:49:27 +0100
Subject: Re: gcc cannot recognize "0xe+0x1"
References: <22bb74350903012021qfce22d0v9d3ca880d57e5@mail.gmail.com>

Tadahito Kobayashi <kovaltan@gmail.com> writes:

>         return 0xe+0x1 ;

0xe+0x1 forms a single preprocessing token (a pp-number), but cannot be
converted to a valid token.  Add some whitespace around + to break up
the preprocessing token.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Follow-Ups:
- Re: gcc cannot recognize "0xe+0x1"
  - From: Tadahito Kobayashi

References:
- gcc cannot recognize "0xe+0x1"
  - From: Tadahito Kobayashi

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]