From: Xavier Delacour <xavier@fmaudio.net>
To: gcc@gcc.gnu.org
Subject: Typo on http://gcc.gnu.org/gcc-3.0/c++features.html
Date: Fri, 13 Jul 2001 19:39:00 -0000 [thread overview]
Message-ID: <5.1.0.14.0.20010713223716.00a54030@mail.fmaudio.net> (raw)
FYI: http://gcc.gnu.org/gcc-3.0/c++features.html has a typo.
...obscure cases, functions with the same type could have the same mangled
name. This bug caused compiler crashes, link-time clashes, and debugger
************crahses************. Fixing this bug required breaking ...
-Xavier
next reply other threads:[~2001-07-13 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 19:39 Xavier Delacour [this message]
2001-07-13 22:20 ` PATCH for " Gerald Pfeifer
2001-07-14 2:56 ` Joseph S. Myers
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=5.1.0.14.0.20010713223716.00a54030@mail.fmaudio.net \
--to=xavier@fmaudio.net \
--cc=gcc@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).