From: Joe Buck <jbuck@synopsys.com>
To: gregg@eoeml.gtri.gatech.edu (Greg Galloway)
Cc: egcs@cygnus.com
Subject: Re: egcs-971016/libstc++/stl/hashtable patch (revised)
Date: Fri, 17 Oct 1997 19:44:00 -0000 [thread overview]
Message-ID: <199710172339.QAA22589@atrus.synopsys.com> (raw)
In-Reply-To: <199710172048.QAA12071@nospokes.gtri.gatech.edu>
> * hashtable.h(__stl_prime_list): Added literal constant suffixes to
> suppress warnings about integer constant which is too large.
> (new_node): Moved return stmt outside try block to suppress warning.
We aren't maintaining the STL files; SGI is. I think we'll have to send
bugs and patches to them, unless we want to fork (do we?). They've
generally been fairly cooperative.
next prev parent reply other threads:[~1997-10-17 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-17 15:05 Greg Galloway
1997-10-17 19:44 ` Joe Buck [this message]
1997-10-17 20:51 ` Jeffrey A Law
1997-10-18 12:17 ` Joe Buck
1997-10-20 20:41 ` Oleg Krivosheev
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=199710172339.QAA22589@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=gregg@eoeml.gtri.gatech.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).