public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "torvald at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/51031] build error in libitm (how to disable trans-mem???) Date: Wed, 09 Nov 2011 12:38:00 -0000 [thread overview] Message-ID: <bug-51031-4-5mCJnQSmY6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51031-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51031 --- Comment #5 from torvald at gcc dot gnu.org 2011-11-09 12:28:28 UTC --- The weak alias issue has been resolved in rev 181182. The TLS thingy in 181163. Regarding the vector loads/stores and your assembler not knowing about .cfi, I don't know. Perhaps we just disable TM on Darwin, or can you provide a patch?
next prev parent reply other threads:[~2011-11-09 12:28 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-08 14:52 [Bug bootstrap/51031] New: " vincenzo.innocente at cern dot ch 2011-11-08 14:57 ` [Bug bootstrap/51031] " dominiq at lps dot ens.fr 2011-11-09 8:58 ` vincenzo.innocente at cern dot ch 2011-11-09 11:48 ` fxcoudert at gcc dot gnu.org 2011-11-09 12:12 ` redi at gcc dot gnu.org 2011-11-09 12:38 ` torvald at gcc dot gnu.org [this message] 2011-11-09 13:43 ` vincenzo.innocente at cern dot ch 2011-11-09 13:55 ` dominiq at lps dot ens.fr 2011-11-09 17:03 ` howarth at nitro dot med.uc.edu 2011-11-09 21:38 ` howarth at nitro dot med.uc.edu 2011-11-09 21:45 ` howarth at nitro dot med.uc.edu 2011-11-10 0:38 ` howarth at nitro dot med.uc.edu 2011-11-10 1:49 ` kargl at gcc dot gnu.org 2011-11-10 2:28 ` rth at gcc dot gnu.org 2011-11-10 2:29 ` howarth at nitro dot med.uc.edu 2011-11-10 10:01 ` vincenzo.innocente at cern dot ch 2011-11-10 10:11 ` dominiq at lps dot ens.fr 2011-11-10 14:47 ` howarth at nitro dot med.uc.edu
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-51031-4-5mCJnQSmY6@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).