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 target/14537] sparc-rtems predefines unix
Date: Wed, 07 Apr 2004 12:56:00 -0000 [thread overview]
Message-ID: <20040407125612.6206.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040311194251.14537.joel@gcc.gnu.org>
------- Additional Comments From joel at oarcorp dot com 2004-04-07 12:56 -------
Subject: Re: sparc-rtems predefines unix
pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-04-07 02:57 -------
> This patch was okayed for 3.4.0 but never applied, Mark I know you do not want any
> patch which can cause many problems at this point as we are about to release but is this
> still okay to apply for 3.4.0? Joel if Mark says it is okay, then please apply right away as
> the release is near.
>
I have not committed this because I do not have a working
3.4.x sparc-rtems toolset. I got side-tracked with
the cross gnatmake and generic *-rtems run-time issues.
So this patch is off the table for 3.4.0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14537
next prev parent reply other threads:[~2004-04-07 12:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 19:42 [Bug target/14537] New: " joel at gcc dot gnu dot org
2004-03-11 19:43 ` [Bug target/14537] " joel at gcc dot gnu dot org
2004-03-11 19:47 ` joel at gcc dot gnu dot org
2004-03-11 20:24 ` joel at gcc dot gnu dot org
2004-03-11 21:36 ` mmitchel at gcc dot gnu dot org
2004-03-13 16:06 ` gdr at gcc dot gnu dot org
2004-03-22 2:23 ` joel at gcc dot gnu dot org
2004-04-07 2:57 ` pinskia at gcc dot gnu dot org
2004-04-07 12:56 ` joel at oarcorp dot com [this message]
2004-05-29 23:12 ` mmitchel at gcc dot gnu dot org
[not found] <bug-14537-296@http.gcc.gnu.org/bugzilla/>
2005-10-22 8:34 ` ebotcazou at gcc dot gnu dot 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=20040407125612.6206.qmail@sources.redhat.com \
--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).