public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gschafer at zip dot com dot au" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/787] New: nptl pthread.h needs fix for GCC-4 bootstraps
Date: Sun, 13 Mar 2005 03:46:00 -0000	[thread overview]
Message-ID: <20050313034556.787.gschafer@zip.com.au> (raw)

This trunk change is needed on the 2.3 branch.

2005-02-07  Richard Henderson  <rth@redhat.com>

        * sysdeps/pthread/pthread.h (__sigsetjmp): Use pointer as first
        argument.


Here's where it went in on the trunk:

  http://sources.redhat.com/ml/glibc-cvs/2005-q1/msg00303.html

More info in the GCC BZ here:

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

-- 
           Summary: nptl pthread.h needs fix for GCC-4 bootstraps
           Product: glibc
           Version: 2.3.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
        AssignedTo: drepper at redhat dot com
        ReportedBy: gschafer at zip dot com dot au
                CC: glibc-bugs at sources dot redhat dot com
OtherBugsDependingO 724
             nThis:


http://sources.redhat.com/bugzilla/show_bug.cgi?id=787

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2005-03-13  3:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-13  3:46 gschafer at zip dot com dot au [this message]
2005-03-13  3:53 ` [Bug nptl/787] " cvs-commit at gcc dot gnu dot org
2005-03-15  7:25 ` jakub at redhat 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=20050313034556.787.gschafer@zip.com.au \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.com \
    /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).