public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/51140] libstdc++-v3/libsupc++/eh_tm.cc:48: undefined reference to `___sync_sub_and_fetch_4' Date: Tue, 15 Nov 2011 13:53:00 -0000 [thread overview] Message-ID: <bug-51140-4-BBN2IwBgZi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51140-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51140 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-11-15 13:12:20 UTC --- That guard should be added to eh_tm.cc but ... don't build for i386-* because that targets the 80386 processor, which doesn't have the required atomic operations, and I *really doubt you're running on an 80386 so there's no reason to unnecessary cripple your code. you should configure for i486-pc-mingw32 or better, whatever is the lowest spec you want to be able to run the generated code on
next prev parent reply other threads:[~2011-11-15 13:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-15 12:40 [Bug libstdc++/51140] New: " cestrauss at gmail dot com 2011-11-15 12:45 ` [Bug libstdc++/51140] " cestrauss at gmail dot com 2011-11-15 13:53 ` redi at gcc dot gnu.org [this message] 2011-11-18 0:24 ` paolo.carlini at oracle dot com 2011-11-22 21:50 ` cestrauss at gmail 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-51140-4-BBN2IwBgZi@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).