public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "truedfx at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/31869]  New: stringifying empty macros
Date: Tue, 08 May 2007 19:31:00 -0000	[thread overview]
Message-ID: <bug-31869-9631@http.gcc.gnu.org/bugzilla/> (raw)

#include <stdio.h>

#define MKSTR(x) STR(x)
#define STR(x) #x
#define EMPTY /* nothing */

int main(void) {
    puts(MKSTR(.EMPTY.));
    puts(MKSTR(.EMPTY .));
}

Using gcc 4.1.2, configured with
../gcc-4.1.2/configure --prefix=$HOME/gcc --enable-languages=c,c++
--disable-multilib, on x86_64-pc-linux-gnu, this program prints out

..
..

rather than

..
. .

as I would expect.


-- 
           Summary: stringifying empty macros
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: truedfx at gentoo dot org


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


             reply	other threads:[~2007-05-08 19:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 19:31 truedfx at gentoo dot org [this message]
2007-05-09  2:14 ` [Bug preprocessor/31869] " pinskia at gcc dot gnu dot org
2007-05-09  4:01 ` neil at gcc dot gnu dot org
2007-05-09 23:33 ` truedfx at gentoo dot org
2007-12-28 20:59 ` truedfx at gentoo dot org
2009-03-29 23:30 ` jsm28 at gcc dot gnu dot org
2009-04-12 22:20 ` jsm28 at gcc dot gnu dot org
2009-04-12 22:23 ` 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-31869-9631@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).