public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gnu.org
To: gcc-gnats@gcc.gnu.org
Cc: wall@chop.swmed.edu
Subject: libstdc++/4146: input, num_get, regression from 2.95
Date: Mon, 27 Aug 2001 11:46:00 -0000 [thread overview]
Message-ID: <20010827184030.32623.qmail@sourceware.cygnus.com> (raw)
>Number: 4146
>Category: libstdc++
>Synopsis: input, num_get, regression from 2.95
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Aug 27 11:46:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: wall@chop.swmed.edu
>Release: gcc-3.x
>Organization:
>Environment:
linux
>Description:
http://gcc.gnu.org/ml/libstdc++/2001-08/msg00191.html
In general, making people wade through 4 files of code to fix a bug is a guarantee of a DOA bug report. If you can simplify this down to one file, or one function, or say 5 lines, your chances of getting it fixed in some sane time schedule go waaaaaaaay up.
That being said, I'll try to look at this in the next month or so.
-benjamin
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-08-27 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 11:46 bkoz [this message]
2001-10-29 10:25 bkoz
2001-11-23 1:46 bkoz
2001-11-23 1:53 bkoz
2001-12-05 14:35 bkoz
2001-12-05 14:46 bkoz
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=20010827184030.32623.qmail@sourceware.cygnus.com \
--to=bkoz@gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=wall@chop.swmed.edu \
/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).