Fw: Possible GCC Bug

[Nick Fleming]

Ok - hope fully this bug report is now going to the right place : -)
Sorry for any annoyance !
-NickF.

----- Original Message ----- 
From: Free Software Foundation <gnu@gnu.org>
To: Nick Fleming <marmalade@x-stream.co.uk>
Sent: Saturday, April 15, 2000 8:55 AM
Subject: Re: Possible GCC Bug


> Nick Fleming wrote:
> > Sorry about this but..
> > 
> > I think I've found a tiny bug in GCC.
> 
> Please send GCC bug reports to <bug-gcc@gnu.org>.
> 
> > (Version 2.95.2 19991024 (release)
> > 
> > - while using djgpp's rhide program.
> > 
> > A snippet from my code :
> > 
> > 0xff, // 00000000  // [
> > 0x3c, // 00111100
> > 0x30, // 00110000
> > 0x30, // 00110000
> > 0x30, // 00110000
> > 0x30, // 00110000
> > 0x3c, // 00111100
> > 0xff, // 00000000
> > 
> > 0xff, // 00000000  // \
> > 0x60, // 01100000
> > 0x70, // 01110000
> > 0x38, // 00111000
> > 0x1c, // 00011100
> > 0x0e, // 00001110
> > 0x06, // 00000110
> > 0x00, // 00000000
> > 
> > 0xff, // 00000000  // ]
> > 0x3c, // 00111100
> > 0x0c, // 00001100
> > 0x0c, // 00001100
> > 0x0c, // 00001100
> > 0x0c, // 00001100
> > 0x3c, // 00111100
> > 0x00, // 00000000
> > 
> > In the above snippet of code, the second group of  bytes has a row missing when
> > compiled.. To correct it I have to write the first line as follows:
> > 
> > 0xff, // 00000000  // '\'
> > 
> > I think gcc's scanner is interpreting the slash as a special character, rather than just
> > skipping it as it should as it is part of a single line comment.
> > 
> > Hope this is some use, if not please pass it on to someone who needs to know
> > this sort of thing. Thanks.
> > 
> > Regards,
> > 
> > Nick. F.
> > 
> 
> -- 
> Bradley M. Kuhn, Assistant to the President of the FSF
> Free Software Foundation     |  Phone: +1-617-542-5942
> 59 Temple Place, Suite 330   |  Fax:   +1-617-542-2652
> Boston, MA 02111-1307  USA   |  Web:   http://www.gnu.org
>