public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Francois-Xavier Kowalski <francois-xavier.kowalski@hp.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/10865: [ia64] gcc -pthread does not add -D_REENTRANT Date: Tue, 20 May 2003 07:46:00 -0000 [thread overview] Message-ID: <20030520074601.18901.qmail@sources.redhat.com> (raw) The following reply was made to PR target/10865; it has been noted by GNATS. From: Francois-Xavier Kowalski <francois-xavier.kowalski@hp.com> To: ljrittle@gcc.gnu.org, francois-xavier.kowalski@hp.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jean-pierre.joannin@hp.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: target/10865: [ia64] gcc -pthread does not add -D_REENTRANT Date: Tue, 20 May 2003 09:38:50 +0200 Hello, [sorry for the direct replay, but I cannot find any "Edit PR" button on the page below & on the entire gants/gcc web. Thanks to point me to a link, so that I can copy/paste the below in the gnats database]. "-pthread" is documented as an RS6000/PowerPC option only: <http://gcc.gnu.org/onlinedocs/gcc-3.2.2/gcc/RS-6000-and-PowerPC-Options.html#RS%2f6000%20and%20PowerPC%20Options> Quoting: |-pthread| Adds support for multithreading with the pthreads library. This option sets flags for both the preprocessor and linker. However, this option exists for every architectures I worked with (HP-UX, Linux, ia32, ia64...). It is even reported as part of the gcc specs: RedHat 8.0 / i386: gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib --enable-__cxa_atexit Thread model: *posix* gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) Debian Sarge / ia64: gcc-3.2 -v Reading specs from /usr/lib/gcc-lib/ia64-linux/3.2.3/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-objc-gc ia64-linux Thread model: *posix* gcc version 3.2.3 20030309 (Debian prerelease) So I have always assumed (as it always worked) that the description for RS6000/PowerPC was Ok for every supported architecture. What I can observe in the current GCC I am using is that the linker option (-lpthread) is set, but not the pre-compiler option -- FiX ljrittle@gcc.gnu.org wrote: >Synopsis: [ia64] gcc -pthread does not add -D_REENTRANT > >State-Changed-From-To: open->feedback >State-Changed-By: ljrittle >State-Changed-When: Tue May 20 00:19:36 2003 >State-Changed-Why: > [Before responding, I checked the gcc documentation that shipped > with both FSF gcc 3.2.2 and FSF gcc 3.3.] > > Question: To which documentation are you referring? To my knowledge, there was no documentation shipped with FSF gcc > 3.2.X or FSF gcc 3.3 which claims that -D_REENTRANT is added > when -pthread is present. It is true that some ports do indeed > add it under that condition however I can find no documentation > on the matter. > >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10865 > > -- Francois-Xavier "FiX" KOWALSKI /_ __ Tel: +33 (0)4 76 14 63 27 OpenCall Business Unit -- OCBU / //_/ Fax: +33 (0)4 76 14 43 23 Signalling Products / HP Telnet: 779-6327 http://www.hp.com/go/opencall i n v e n t
next reply other threads:[~2003-05-20 7:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-20 7:46 Francois-Xavier Kowalski [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-20 0:19 ljrittle
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=20030520074601.18901.qmail@sources.redhat.com \ --to=francois-xavier.kowalski@hp.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).