From: Andreas Jaeger <aj@arthur.rhein-neckar.de>
To: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
Cc: gavin@cygnus.com, scottrobertladd@yahoo.com, gcc@gcc.gnu.org,
scott@coyotegulch.com
Subject: Re: Support for C9X in gcc?
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <u8906jceqy.fsf@arthur.rhein-neckar.de> (raw)
Message-ID: <19990930180200.onMsCCGpLyQ7y4AzfwSWW7ys4-JQJo7aGxJyntBsZdA@z> (raw)
In-Reply-To: <199909070645.IAA00505@mira.isdn.cs.tu-berlin.de>
>>>>> Martin v Loewis writes:
>> As Zack said, most of the C9X work is in the library, but there
>> is some compiler work needed. This work is on my list of things to
>> do, but so is alot of other stuff :-).
> Could we come up with a list, just so that people know what needs to
> be done? Currently, I see
> - complex (as indicated by Zack),
> - preprocessor changes (which ones are needed, which ones are done?),
> What else?
AFAIK some printf specifiers are new in C9X and are not supported by
gcc. glibc already supports the specifiers but every usage leads to
warnings by gcc. If you need further details, ask me. I've send this
once as a bug report.
Andreas
--
Andreas Jaeger aj@arthur.rhein-neckar.de jaeger@informatik.uni-kl.de
for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de
next prev parent reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-03 10:37 Scott Ladd
1999-09-03 10:43 ` Zack Weinberg
1999-09-30 18:02 ` Zack Weinberg
1999-09-03 11:44 ` Gavin Romig-Koch
1999-09-06 23:48 ` Martin v. Loewis
1999-09-07 1:08 ` Geoff Keating
1999-09-30 18:02 ` Geoff Keating
1999-09-07 1:28 ` Andreas Jaeger [this message]
1999-09-30 18:02 ` Andreas Jaeger
1999-09-07 8:40 ` Andi Kleen
1999-09-30 18:02 ` Andi Kleen
1999-09-07 9:15 ` Gerald Pfeifer
1999-09-07 15:24 ` Martin v. Loewis
1999-09-30 18:02 ` Martin v. Loewis
1999-09-30 18:02 ` Gerald Pfeifer
1999-09-30 18:02 ` Martin v. Loewis
1999-09-30 18:02 ` Gavin Romig-Koch
1999-09-30 18:02 ` Scott Ladd
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=u8906jceqy.fsf@arthur.rhein-neckar.de \
--to=aj@arthur.rhein-neckar.de \
--cc=gavin@cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=martin@mira.isdn.cs.tu-berlin.de \
--cc=scott@coyotegulch.com \
--cc=scottrobertladd@yahoo.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).