public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/35816] libstdc++ build during bootstrap is optimizing away atomic builtin check Date: Tue, 15 Apr 2008 00:27:00 -0000 [thread overview] Message-ID: <20080415002630.752.qmail@sourceware.org> (raw) In-Reply-To: <bug-35816-15855@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from bkoz at gcc dot gnu dot org 2008-04-15 00:26 ------- Subject: Bug 35816 Author: bkoz Date: Tue Apr 15 00:25:45 2008 New Revision: 134305 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=134305 Log: 2008-04-14 Benjamin Kosnik <bkoz@redhat.com> PR libstdc++/35816 * acinclude.m4 (GLIBCXX_ENABLE_ATOMIC_BUILTINS): Set CXXFLAGS to -O0 when checking for atomic builtins. * configure: Regenerate. Modified: branches/gcc-4_3-branch/libstdc++-v3/ChangeLog branches/gcc-4_3-branch/libstdc++-v3/acinclude.m4 branches/gcc-4_3-branch/libstdc++-v3/configure -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35816
prev parent reply other threads:[~2008-04-15 0:27 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-03 16:02 [Bug libstdc++/35816] New: libstdc++ built during bootstrap is pulling in host g++ support for atomic builtins oblivian at users dot sourceforge dot net 2008-04-03 17:35 ` [Bug libstdc++/35816] " oblivian at users dot sourceforge dot net 2008-04-03 20:46 ` [Bug libstdc++/35816] libstdc++ build during bootstrap is optimizing away atomic builtin check oblivian at users dot sourceforge dot net 2008-04-14 22:49 ` bkoz at gcc dot gnu dot org 2008-04-14 23:54 ` bkoz at gcc dot gnu dot org 2008-04-15 0:27 ` bkoz at gcc dot gnu dot org 2008-04-15 0:27 ` bkoz at gcc dot gnu dot org [this message]
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=20080415002630.752.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).