Your message dated Mon, 27 May 2002 22:51:57 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Not a bug
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 14 Feb 2001 02:58:35 +0000
>From [EMAIL PROTECTED] Tue Feb 13 20:58:35 2001
Return-path: <[EMAIL PROTECTED]>
Received: from (gilgamesh.uruk) [::ffff:207.144.234.196] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 14Ss9K-0003Dk-00; Tue, 13 Feb 2001 20:58:35 -0600
Received: from localhost [127.0.0.1] (foobar)
        by gilgamesh.uruk with esmtp (Exim 3.22 #1 (Debian))
        id 14Ss96-00006w-00; Tue, 13 Feb 2001 21:58:20 -0500
Date: Tue, 13 Feb 2001 21:58:20 -0500 (EST)
From: Jim Bray <[EMAIL PROTECTED]>
X-Sender:  <[EMAIL PROTECTED]>
To:  <[EMAIL PROTECTED]>
Subject: gcc/cpp/stddef.h
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]

Package: gcc
Version: 1:2.95.3-5

 Garbage before an include of stddef.h produces the following error:
gilgamesh:~[1]gcc gccbug.c
In file included from gccbug.c:2:
/usr/lib/gcc-lib/i386-linux/2.95.3/include/stddef.h:118: syntax error before
`typedef'

instead of telling one that there is random garbage on line 1. If one
separates 'RandomGarbage' into 'Random Garbage', the error is slightly more
informative:

gilgamesh:~[1]gcc gccbug.c
gccbug.c:1: parse error before `Garbage'
In file included from gccbug.c:2:
/usr/lib/gcc-lib/i386-linux/2.95.3/include/stddef.h:118: syntax error before
`typedef'

gccbug.c:

RandomGarbage
#include <stddef.h>

int main()
{
}

Jim             http://as220.org/jb


---------------------------------------
Received: (at 85908-done) by bugs.debian.org; 27 May 2002 20:54:26 +0000
>From [EMAIL PROTECTED] Mon May 27 15:54:26 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 17CRVY-0006O5-00; Mon, 27 May 2002 15:54:24 -0500
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
        by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id WAA25608
        for <[EMAIL PROTECTED]>; Mon, 27 May 2002 22:51:58 +0200 (MET DST)
Received: (from [EMAIL PROTECTED])
        by bolero.cs.tu-berlin.de (8.11.6+Sun/8.9.3) id g4RKpvi25581;
        Mon, 27 May 2002 22:51:57 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Mon, 27 May 2002 22:51:57 +0200
To: [EMAIL PROTECTED]
Subject: Not a bug
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]

Audit trail taken from
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3487&database=gcc

Audit Trail:

State-Changed-From-To: open->analyzed
State-Changed-By: neil
State-Changed-When: Mon Jul  2 04:07:24 2001
State-Changed-Why:
    I'm far from convinced this is a bug, or even undesirable
    behaviour - the compiler reports its position when it finds a syntax
    error.  In some weird cases, this happens to be in the header file.
    
    In any case, the cause is the front end and not the preprocessor.
    I'll let a C front end maintainer decide.

State-Changed-From-To: analyzed->closed
State-Changed-By: rodrigc
State-Changed-When: Sat Feb 23 18:36:30 2002
State-Changed-Why:
    Not a bug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Reply via email to