From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: "H. J. Lu" <hjl@lucon.org>
Cc: <gcc@gcc.gnu.org>, GNU C Library <libc-alpha@sources.redhat.com>
Subject: Re: C ABI changes between gcc 2.96 and gcc 3.2?
Date: Mon, 14 Oct 2002 19:13:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0210150131580.8838-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20021014170206.A3933@lucon.org>
On Mon, 14 Oct 2002, H. J. Lu wrote:
> Is that a known issue? I guess I can extract a testcase out of it. I
> think it may impact people who try to use gcc 2.96 with glibc compiled
> with gcc 3.2.
This would be the broken <stdbool.h> in 2.9x. An untested patch for that
is at <http://gcc.gnu.org/ml/gcc/2002-09/msg00797.html> (without the
removal of the configure test for <stdbool.h> that should accompany it).
Unless glibc uses or used <stdbool.h> this is irrelevant to glibc.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2002-10-15 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 18:36 H. J. Lu
2002-10-14 19:13 ` Joseph S. Myers [this message]
2002-10-14 23:28 ` H. J. Lu
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=Pine.LNX.4.33.0210150131580.8838-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=hjl@lucon.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).