public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gnicholls@bluephoenixsolutions.com
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/7457: failure preprocessing ## directive
Date: Wed, 31 Jul 2002 12:56:00 -0000	[thread overview]
Message-ID: <20020731195039.10701.qmail@sources.redhat.com> (raw)


>Number:         7457
>Category:       preprocessor
>Synopsis:       failure preprocessing ## directive
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 31 12:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Gregory Nicholls
>Release:        gcc v3.1
>Organization:
>Environment:
hpux11 and solaris
>Description:
The following construct fails compilation:-
#define LIB_SUFF ".so"
#define SV_MODULE_NAME_STR "libdrv"##LIB_SUFF

 This used to work on an earlier gcc and it also works on native
aix c89 as well as native hpux cc. This is old code so I'm not sure if 
it's really a gcc bug or 'undefined behaviour'. In any case it's
easy to repeat.
>How-To-Repeat:
compile supplied test program. Should fail with the following:
gcc_test.c:6:29: warning: pasting ""libdrv"" and "LIB_SUFF" does not give a vali
d preprocessing token
>Fix:
Dont' know <grin>.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/x-unknown-content-type-cfile; name="gcc_test.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gcc_test.c"

I2RlZmluZSBMSUJfU1VGRiAiLnNvIg0KI2RlZmluZSBTVl9NT0RVTEVfTkFNRV9TVFIgImxpYmRy
diIjI0xJQl9TVUZGDQoNCmludCBtYWluKGludCBhcmdjLCBjaGFyICoqYXJndikNCnsNCiBwcmlu
dGYoIk1vZHVsZSBOYW1lWyVzXVxuIixTVl9NT0RVTEVfTkFNRV9TVFIpOw0KIHJldHVybigwKTsN
Cn0NCg==


             reply	other threads:[~2002-07-31 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 12:56 gnicholls [this message]
2002-07-31 13:16 Zack Weinberg
2002-07-31 15:21 neil
2002-08-01  5:46 Gregory Nicholls

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=20020731195039.10701.qmail@sources.redhat.com \
    --to=gnicholls@bluephoenixsolutions.com \
    --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).