From: martin@v.loewis.de (Martin v. Löwis)
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: gcc@gcc.gnu.org, libc-alpha@sources.redhat.com
Subject: Re: Miscompilation of glibc with CVS mainline
Date: Thu, 02 Jan 2003 20:25:00 -0000 [thread overview]
Message-ID: <m3lm235mi1.fsf@mira.informatik.hu-berlin.de> (raw)
In-Reply-To: <m33cob5p62.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> > Isn't this going to cause a problem with the gcc weak extension
>
> Any program that uses the weak extension is violating the standard, so
> gcc is allowed to also violate the standard in a useful way in such a
> case.
More precisely, it's not a violation, it is an extension (4p8); a
conforming implementation must document what the extensions are and
must diagnose usage of extensions.
For the GCC weak extension, the relevant clause of the standard does
not apply: in a strictly conforming program, the weak extension cannot
be used. The GCC documentation fails to mention that taking the
address of a weak function may yield a null pointer; this is a
documentation bug.
Regards,
Martin
next prev parent reply other threads:[~2003-01-02 20:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 17:43 John David Anglin
2003-01-02 13:18 ` Andreas Jaeger
2003-01-02 13:27 ` Jakub Jelinek
2003-01-02 13:53 ` Andreas Jaeger
2003-01-02 14:41 ` Andreas Jaeger
2003-01-02 21:10 ` Andreas Jaeger
2003-01-02 17:38 ` John David Anglin
2003-01-02 17:48 ` "Martin v. Löwis"
2003-01-02 18:52 ` John David Anglin
2003-01-02 18:58 ` Paul Jarc
2003-01-02 19:10 ` Dale Johannesen
2003-01-02 19:16 ` John David Anglin
2003-01-02 19:26 ` Paul Jarc
2003-01-02 20:25 ` Martin v. Löwis [this message]
2003-01-02 22:11 ` Richard Henderson
2003-01-03 1:02 ` John David Anglin
2003-01-03 1:35 ` Richard Henderson
2003-01-02 19:42 ` Ulrich Drepper
2003-01-02 22:16 ` Richard Henderson
2003-01-03 0:14 ` Fergus Henderson
-- strict thread matches above, loose matches on Subject: below --
2003-01-04 18:54 Robert Dewar
2003-01-04 17:52 Robert Dewar
[not found] <no.id>
2003-01-02 17:48 ` John David Anglin
2003-01-02 17:54 ` Jakub Jelinek
2003-01-02 18:58 ` John David Anglin
2003-01-02 17:57 ` Daniel Jacobowitz
2003-01-01 13:37 Andreas Jaeger
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=m3lm235mi1.fsf@mira.informatik.hu-berlin.de \
--to=martin@v.loewis.de \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sources.redhat.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).