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++/39796] cin/cout/cerr constructors should run at high priority when possible
Date: Fri, 17 Apr 2009 15:06:00 -0000	[thread overview]
Message-ID: <20090417150633.32049.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39796-1313@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from paolo dot carlini at oracle dot com  2009-04-17 15:06 -------
I see. I would be tempted to ask you to propose a fix at once, seems pretty
simple, basically a bit of configury and very few lines of actual code.
However, I wonder if we have something similar elsewhere, I seem to remember
something for the memory allocators, for example, but possibly by now we have
static locals everywhere to avoid completely running into such priority issues.
Another area which probably should be audited is that of locale. What do you
think?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39796


  reply	other threads:[~2009-04-17 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 14:26 [Bug libstdc++/39796] New: " ian at airs dot com
2009-04-17 15:06 ` paolo dot carlini at oracle dot com [this message]
2009-04-18  5:40 ` [Bug libstdc++/39796] " ian at airs dot com
2009-04-21  2:47 ` bkoz at gcc dot gnu dot org
     [not found] <bug-39796-4@http.gcc.gnu.org/bugzilla/>
2012-01-03 16:41 ` redi at gcc dot gnu.org
2022-11-06 16:16 ` cvs-commit at gcc dot gnu.org
2023-02-03 19:49 ` pinskia 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=20090417150633.32049.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).