public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Hoenle2007@kayser-threde.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/50703] std::stringstream not thread-safe Date: Mon, 17 Oct 2011 08:17:00 -0000 [thread overview] Message-ID: <bug-50703-4-U0gr464Hcp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50703-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50703 --- Comment #7 from Hoenle2007@kayser-threde.com 2011-10-17 08:17:21 UTC --- @Jonathan: You ask "was gcc built with a non-default value for --enable-clocale ?". I don't think so. We perform cross development on Windows with MinGW as supported out-of-the-box by the RTEMS operating system distribution. With that distribution the cross compilation tools come already pre-compiled. Maybe the following gcc output helps: $ sparc-rtems-gcc -v Reading specs from c:/opt/rtems-4.8-mingw/bin/../lib/gcc/sparc-rtems/4.2.4/specs Target: sparc-rtems Configured with: ../gcc-4.2.4/configure --target=sparc-rtems --host i686-mingw32 --build i486-slackware-linux --with-gnu-as --with-gnu-ld --with-newlib --verbose --enable-threads --enable-languages=c,c++ --disable-nls --prefix=/opt/rtems-4.8-mingw --enable-version-specific-runtime-libs --with-system-zlib --disable-libstdcxx-pch --disable-win32-registry --without-included-gettext Thread model: rtems gcc version 4.2.4 ----------------- @Paolo: We never access a std::stringstream object from different threads but always from a single thread. When we share objects between threads, we protect them by a pthread mutex. I will perform a test with a new GCC/libstdc++ probably mid November. In case the problem persists I will try to set up a short, self contained reproducer. ----------------- Regards Alfred
next prev parent reply other threads:[~2011-10-17 8:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-12 15:35 [Bug libstdc++/50703] New: " Hoenle2007@kayser-threde.com 2011-10-12 15:37 ` [Bug libstdc++/50703] " Hoenle2007@kayser-threde.com 2011-10-12 15:39 ` paolo.carlini at oracle dot com 2011-10-13 7:57 ` Hoenle2007@kayser-threde.com 2011-10-13 8:12 ` redi at gcc dot gnu.org 2011-10-13 12:02 ` redi at gcc dot gnu.org 2011-10-13 12:23 ` paolo.carlini at oracle dot com 2011-10-17 8:17 ` Hoenle2007@kayser-threde.com [this message] 2013-08-04 10:48 ` liuxiaopi349 at hotmail 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=bug-50703-4-U0gr464Hcp@http.gcc.gnu.org/bugzilla/ \ --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).