public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "johandefries at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/30805]  New: Internal compiler error when using "x##,##__VA_ARGS__" in macro
Date: Thu, 15 Feb 2007 13:15:00 -0000	[thread overview]
Message-ID: <bug-30805-14101@http.gcc.gnu.org/bugzilla/> (raw)

The 2-line source that triggers the error:

#define A(x,...) x##,##__VA_ARGS__
A(1)

Error message:
a.c:6: internal compiler error: Geannuleerd
Please submit a full bug report

The source file is from:
http://www.kernel.org/git/?p=linux/kernel/git/josh/sparse.git;a=blob;f=validation/preprocessor13.c;hb=0.2

My system:
Linux Knoppix 2.6.19 #7 SMP PREEMPT Sun Dec 17 22:01:07 CET 2006 i686 GNU/Linux

The bug is triggerd by al 4 compilers on my system. 
gcc-3.3 (GCC) 3.3.6 (Debian 1:3.3.6-13)
gcc-3.4 (GCC) 3.4.6 (Debian 3.4.6-4)
gcc-4.0 (GCC) 4.0.4 20060904 (prerelease) (Debian 4.0.3-7)
gcc-4.1 (GCC) 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)


-- 
           Summary: Internal compiler error when using "x##,##__VA_ARGS__"
                    in macro
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: johandefries at gmail dot com
  GCC host triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30805


             reply	other threads:[~2007-02-15 13:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 13:15 johandefries at gmail dot com [this message]
2007-02-16  1:34 ` [Bug preprocessor/30805] [4.1/4.2/4.3 Regression] " pinskia at gcc dot gnu dot org
2007-02-19 21:10 ` mmitchel at gcc dot gnu dot org
2007-02-19 22:20 ` joseph at codesourcery dot com
2007-03-05  3:56 ` mmitchel at gcc dot gnu dot org
2007-04-16 19:10 ` bonzini at gnu dot org
2007-10-31 17:37 ` tromey at gcc dot gnu dot org
2007-10-31 19:12 ` tromey at gcc dot gnu dot org
2007-11-01 18:21 ` tromey at gcc dot gnu dot org
2007-11-01 18:28 ` [Bug preprocessor/30805] [4.1/4.2 " jakub at gcc dot gnu dot org
2007-11-01 23:25 ` jakub at gcc dot gnu dot org
2007-11-01 23:34 ` tromey at gcc dot gnu dot org
2007-11-01 23:39 ` tromey at gcc dot gnu dot org
2008-07-04 21:57 ` [Bug preprocessor/30805] [4.2 " jsm28 at gcc dot gnu dot org
2009-03-30 21:35 ` jsm28 at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30805-14101@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).