public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: bjornw@planetarion.com, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libstdc++/4220: min/max problem in std_limits.h
Date: Thu, 04 Apr 2002 12:06:00 -0000 [thread overview]
Message-ID: <20020404200621.12792.qmail@sources.redhat.com> (raw)
Synopsis: min/max problem in std_limits.h
State-Changed-From-To: analyzed->closed
State-Changed-By: bkoz
State-Changed-When: Thu Apr 4 12:06:19 2002
State-Changed-Why:
Lacking testcase, can't reproduce. If you believe this is still in error with gcc-3.1, please refile this bug report with soruces and a proper description.
thanks,
benjamin
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4220
next reply other threads:[~2002-04-04 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 12:06 bkoz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-01 18:49 bkoz
2001-09-04 1:46 bjornw
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=20020404200621.12792.qmail@sources.redhat.com \
--to=bkoz@gcc.gnu.org \
--cc=bjornw@planetarion.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--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).