public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/52569] [4.8 Regression] bootstrap fails on x86_64-apple-darwin10 at revision 185261
Date: Tue, 13 Mar 2012 08:44:00 -0000	[thread overview]
Message-ID: <bug-52569-4-mxlSo1pkCB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52569-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52569

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2012-03-13
         AssignedTo|unassigned at gcc dot       |rguenth at gcc dot gnu.org
                   |gnu.org                     |
   Target Milestone|---                         |4.8.0
     Ever Confirmed|0                           |1

--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-13 08:42:53 UTC ---
Mine.  But I can only guess a fix and not test it.  Basically we now absolutely
require the GTHREAD_ONCE stuff, please have a try providing it for darwin
(I can see a manual page for pthread_once at least).

I see in unwind-dw2-fde-darwin.c:

/* Carefully don't include gthr.h.  */

what's that about?  It looks like that hack no longer works with the
changed condition for using __GTHREAD_MUTEX_INIT_FUNCTION.


  reply	other threads:[~2012-03-13  8:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 19:57 [Bug bootstrap/52569] New: " dominiq at lps dot ens.fr
2012-03-13  8:44 ` rguenth at gcc dot gnu.org [this message]
2012-03-13  8:53 ` [Bug bootstrap/52569] " iains at gcc dot gnu.org
2012-03-13  8:57 ` rguenth at gcc dot gnu.org
2012-03-13 10:02 ` rguenth at gcc dot gnu.org
2012-03-13 10:02 ` rguenth 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=bug-52569-4-mxlSo1pkCB@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: link
Be 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).