public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/9606: performance regression in operator<<(ostream&,int)
Date: Fri, 07 Feb 2003 01:46:00 -0000	[thread overview]
Message-ID: <20030207014600.1635.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/9606; it has been noted by GNATS.

From: Joe Buck <jbuck@synopsys.com>
To: paolo@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/9606: performance regression in operator<<(ostream&,int)
Date: Thu, 6 Feb 2003 17:43:22 -0800

 On Fri, Feb 07, 2003 at 12:49:21AM -0000, paolo@gcc.gnu.org wrote:
 
 > State-Changed-From-To: open->closed
 >     Unfortunately, known, complex issue (see libstdc++/8761
 >     and libstdc++/7076).
 
 It's appropriate to close as a duplicate of 7076, but it doesn't
 seem to have anything to do with 8761.


             reply	other threads:[~2003-02-07  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07  1:46 Joe Buck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-07  0:49 paolo
2003-02-06 23:46 jbuck

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=20030207014600.1635.qmail@sources.redhat.com \
    --to=jbuck@synopsys.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: 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).