public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: francois-xavier.kowalski@hp.com
To: gcc-gnats@gcc.gnu.org
Cc: jean-pierre.joannin@hp.com
Subject: preprocessor/10865: gcc -pthread does not add -D_REENTRANT
Date: Mon, 19 May 2003 15:36:00 -0000	[thread overview]
Message-ID: <20030519153115.23942.qmail@sources.redhat.com> (raw)


>Number:         10865
>Category:       preprocessor
>Synopsis:       gcc -pthread does not add -D_REENTRANT
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 19 15:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     francois-xavier.kowalski@hp.com
>Release:        gcc-3.x
>Organization:
>Environment:
Linux ia64
>Description:
when invoked with option -pthread, gcc-3.x does not add the pre-processor definition -D_REENTRANT, as explained in the documentation & as gcc-2.x was previously doing.

This behaviour is duplicated on the old gcc-3.0.4 on RedHat 7.2 / ia64, then on the same compiler on RedHat Advanced Server 2.1, then on gcc-3.2.3 for Debian Sarge / ia64.

Ref: <http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=84589>

RedHat did not take this bug into account.
>How-To-Repeat:
Steps to Reproduce:
1. get the attached program pthbug.c
2. compile it with gcc -v -pthread -Wall -Wstrict-prototypes pthbug.c
3. note that -D_REENTRANT is not defined

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="pthbug.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="pthbug.c"

I2luY2x1ZGUgPHN0ZGxpYi5oPgojaW5jbHVkZSA8cHRocmVhZC5oPgoKdm9pZCogcnVuKCB2b2lk
KiApOwoKaW50IG1haW4oIGludCBhcmdjLCBjaGFyICphcmd2W10gKQp7CiNpZm5kZWYgX1JFRU5U
UkFOVAojZXJyb3IgIl9SRUVOVFJBTlQgdW5kZWZpbmVkIgojZW5kaWYKCXB0aHJlYWRfdCBjaGls
ZDsKCXB0aHJlYWRfY3JlYXRlKCAmY2hpbGQsIE5VTEwsIHJ1biwgTlVMTCApOwoJZXhpdCggMCAp
Owp9Cgp2b2lkKiBydW4oIHZvaWQqIHAgKQp7CglwdGhyZWFkX2V4aXQoIE5VTEwgKTsKfQo=


                 reply	other threads:[~2003-05-19 15:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030519153115.23942.qmail@sources.redhat.com \
    --to=francois-xavier.kowalski@hp.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=jean-pierre.joannin@hp.com \
    /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).