public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chris at bubblescope dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/31970] set<>::iterator vs type-safety
Date: Sun, 10 Jun 2007 00:10:00 -0000 [thread overview]
Message-ID: <20070610001002.1921.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31970-14562@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from chris at bubblescope dot net 2007-06-10 00:10 -------
While fixing this could stop that illegal code, wouldn't it also lead to
increased code size where you have multiple sets of (for example) ints
templated on different comparitors?
--
chris at bubblescope dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chris at bubblescope dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31970
next prev parent reply other threads:[~2007-06-10 0:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 10:43 [Bug c++/31970] New: g++ compiles incorrect c++ code asp_ at mail dot ru
2007-05-17 14:47 ` [Bug c++/31970] " bangerth at dealii dot org
2007-05-18 7:56 ` asp_ at mail dot ru
2007-05-18 10:33 ` [Bug libstdc++/31970] " pcarlini at suse dot de
2007-05-18 10:33 ` pcarlini at suse dot de
2007-05-18 10:45 ` pcarlini at suse dot de
2007-05-21 15:49 ` [Bug libstdc++/31970] set<>::iterator vs type-safety pcarlini at suse dot de
2007-06-10 0:10 ` chris at bubblescope dot net [this message]
2007-06-10 0:20 ` pcarlini at suse dot de
2007-06-10 8:57 ` chris at bubblescope dot net
2010-02-13 1:44 ` paolo dot carlini at oracle dot com
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=20070610001002.1921.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).