public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs 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: Sat, 18 Apr 2009 05:40:00 -0000 [thread overview] Message-ID: <20090418054025.21272.qmail@sourceware.org> (raw) In-Reply-To: <bug-39796-1313@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from ian at airs dot com 2009-04-18 05:40 ------- You are much more familiar with the library than I am. I don't know if this issue arises anywhere else. cin/cout/cerr is sort of an obvious case. It didn't really occur to me that there might be similar issues elsewhere. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39796
next prev parent reply other threads:[~2009-04-18 5:40 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 ` [Bug libstdc++/39796] " paolo dot carlini at oracle dot com 2009-04-18 5:40 ` ian at airs dot com [this message] 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=20090418054025.21272.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: linkBe 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).