public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joel at oarcorp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/32640] Binding for pthread_sigmask not same as other ports
Date: Thu, 05 Jul 2007 18:30:00 -0000	[thread overview]
Message-ID: <20070705183005.16720.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32640-295@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from joel at oarcorp dot com  2007-07-05 18:30 -------
Created an attachment (id=13853)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13853&action=view)
Patch to make this file compile

With this patch, I have been able to successfully compile GNAT for 7 target
architectures supported by RTEMS, run the ACATS on two of them and an Ada hello
world on most of them.

Could someone please apply this to the head and 4.2 branch before 4.2.1
freezes?


-- 


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


  reply	other threads:[~2007-07-05 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05 18:28 [Bug ada/32640] New: " joel at oarcorp dot com
2007-07-05 18:30 ` joel at oarcorp dot com [this message]
2007-07-05 20:36 ` [Bug ada/32640] [Ada] [4.2 Regression] " laurent at guerby dot net
2007-07-08 14:23 ` laurent at guerby dot net

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=20070705183005.16720.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: 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).