public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/3187: gcc-3.0 prerelease lays down two copies of constructors
Date: Wed, 19 Feb 2003 15:26:00 -0000 [thread overview]
Message-ID: <20030219152600.977.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/3187; it has been noted by GNATS.
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
peter@empeg.com, gcc-prs@gcc.gnu.org
Subject: Re: c++/3187: gcc-3.0 prerelease lays down two copies of
constructors
Date: 19 Feb 2003 16:21:59 +0100
Op wo 19-02-2003, om 16:16 schreef Nathan Sidwell:
> Steven Bosscher wrote:
> > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3187
> >
> >
> > This PR is _really_ old. Last modified over a year and a half ago, so it
> > should go in feedback. It would be even better if this bug is fixed
> > because it's a pretty serious bug IMO.
> no. analyzed is the right state. Why do you think it serious? It does
> not cause miscompilation or reject legal code.
Nope, that's why I didn't say critical. I think it's serious because of
the 20% increase in code size as claimed in the PR.
next reply other threads:[~2003-02-19 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 15:26 Steven Bosscher [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 15:26 Nathan Sidwell
2003-02-19 15:06 Steven Bosscher
2001-06-15 0:53 nathan
2001-06-14 12:16 Philip Blundell
2001-06-14 11:46 peter
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=20030219152600.977.qmail@sources.redhat.com \
--to=s.bosscher@student.tudelft.nl \
--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: 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).