public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/44952] #include <iostream> implies global constructor.
Date: Thu, 15 Jul 2010 18:26:00 -0000 [thread overview]
Message-ID: <20100715182610.31943.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44952-176@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from paolo dot carlini at oracle dot com 2010-07-15 18:26 -------
Let's say we remove that horrible .h from the Summary, since, to be fair,
didn't exist in g.C in the first place ;)
That said, I agree with Jon, by and large, with the following minor additional
observations: 1- I'm pretty sure the library is correct, but we should double
check whether other established and new implementations of the C++ runtime are
trying to do something special, performance-wise - low priority I'm afraid; 2-
As library maintainers we certainly welcome any improvement to the optimizers
improving the code GCC generates for these constructors, because certainly many
user applications could benefit, not just because the library would; -3 While
we are at it, I think we should make sure not regressing on libstdc++/39796, or
even making progress at once. Ideas? (I didn't really manage to study it in any
detail)
--
paolo dot carlini at oracle dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Summary|#include <iostream.h> imply |#include <iostream> implies
|global constructor. |global constructor.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44952
next prev parent reply other threads:[~2010-07-15 18:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 15:51 [Bug libstdc++/44952] New: #include <iostream.h> imply " hubicka at gcc dot gnu dot org
2010-07-15 16:02 ` Andrew Pinski
2010-07-15 16:02 ` [Bug libstdc++/44952] " pinskia at gmail dot com
2010-07-15 16:04 ` rguenth at gcc dot gnu dot org
2010-07-15 16:12 ` hubicka at gcc dot gnu dot org
2010-07-15 16:30 ` pinskia at gcc dot gnu dot org
2010-07-15 16:39 ` redi at gcc dot gnu dot org
2010-07-15 16:45 ` redi at gcc dot gnu dot org
2010-07-15 16:53 ` hubicka at gcc dot gnu dot org
2010-07-15 17:49 ` redi at gcc dot gnu dot org
2010-07-15 18:26 ` paolo dot carlini at oracle dot com [this message]
2010-07-22 0:02 ` [Bug libstdc++/44952] #include <iostream> implies " pinskia at gcc dot gnu dot org
2010-07-22 11:04 ` jakub at gcc dot gnu dot org
2010-07-22 11:25 ` paolo dot carlini at oracle dot com
2010-07-22 11:41 ` jakub at gcc dot gnu dot org
2010-08-19 9:39 ` hubicka at gcc dot gnu dot org
[not found] <bug-44952-4@http.gcc.gnu.org/bugzilla/>
2010-12-14 18:50 ` ccoutant at gcc dot gnu.org
2020-12-10 16:03 ` redi at gcc dot gnu.org
2022-11-03 14:38 ` jason at gcc dot gnu.org
2022-11-03 18:36 ` ppalka at gcc dot gnu.org
2022-11-06 16:16 ` cvs-commit at gcc dot gnu.org
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=20100715182610.31943.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).