public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paul.stoeber@in.stud.tu-ilmenau.de
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/4492: cpp incorrectly omits whitespace in output (affects linux build)
Date: Sat, 06 Oct 2001 08:56:00 -0000	[thread overview]
Message-ID: <200110061557.RAA26354@clouet.rz.tu-ilmenau.de> (raw)

>Number:         4492
>Category:       preprocessor
>Synopsis:       cpp incorrectly omits whitespace in output (affects linux build)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Oct 06 08:56:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Paul Stoeber
>Release:        3.1 20010930 (experimental)
>Organization:
>Environment:
System: Linux tulgey 2.4.9-pre3 #10 Wed Oct 3 16:18:13 UTC 2001 ppc unknown
Architecture: ppc
host: powerpc-unknown-linux-gnu
build: powerpc-unknown-linux-gnu
target: powerpc-unknown-linux-gnu
configured with: ../gcc/configure --prefix=/home/wtq/gcc-inst --enable-languages=c
>Description:
$ cat bug.c
#define A(x) B x
#define B(k)
A(C)
$ /home/wtq/gcc-inst/bin/cpp -v bug.c
Reading specs from /home/wtq/gcc-inst/lib/gcc-lib/powerpc-unknown-linux-gnu/3.1/specs
Configured with: ../gcc/configure --prefix=/home/wtq/gcc-inst --enable-languages=c
Thread model: single
gcc version 3.1 20010930 (experimental)
 /home/wtq/gcc-inst/lib/gcc-lib/powerpc-unknown-linux-gnu/3.1/cpp0 -lang-c -v -DPPC -D__ELF__ -Dpowerpc -D__PPC__ -D__ELF__ -D__powerpc__ -D__PPC -D__powerpc -Acpu=powerpc -Amachine=powerpc -D__CHAR_UNSIGNED__ -D__NO_INLINE__ -D__STDC_HOSTED__=1 -D_CALL_SYSV -D_BIG_ENDIAN -D__BIG_ENDIAN__ -Amachine=bigendian -D_ARCH_PPC -D__unix__ -D__linux__ -Dunix -D__unix -Dlinux -D__linux -Asystem=unix -Asystem=posix bug.c
GNU CPP version 3.1 20010930 (experimental) (cpplib) (PowerPC GNU/Linux)
ignoring nonexistent directory "/home/wtq/gcc-inst/powerpc-unknown-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/include
 /home/wtq/gcc-inst/include
 /home/wtq/gcc-inst/lib/gcc-lib/powerpc-unknown-linux-gnu/3.1/include
 /usr/include
End of search list.
# 1 "bug.c"
# 1 "<builtin>"
# 1 "<command line>"
# 1 "bug.c"


BC
$ 

>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-10-06  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-06  8:56 paul.stoeber [this message]
2001-10-06 10:56 Neil Booth
2001-10-07 23:23 neil

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=200110061557.RAA26354@clouet.rz.tu-ilmenau.de \
    --to=paul.stoeber@in.stud.tu-ilmenau.de \
    --cc=gcc-gnats@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).