From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: eliz@gnu.org, denis.pilat@st.com, gdb-patches@sourceware.org
Subject: Re: [RFA] gdb is broken: missing signal.h checking
Date: Fri, 30 Mar 2007 19:01:00 -0000 [thread overview]
Message-ID: <20070330190106.GA28397@caradoc.them.org> (raw)
In-Reply-To: <200703301853.l2UIrTSg009986@brahms.sibelius.xs4all.nl>
On Fri, Mar 30, 2007 at 08:53:29PM +0200, Mark Kettenis wrote:
> Aha, missed that bit of detail I guess.
It's very recent :-)
> > I believe some projects (binutils and gcc maybe?) draw a distinction
> > between "an ISO C compiler" and "an ISO C standard library" and
> > require the former but not the latter.
>
> The distinction is "Freestanding" versus "Hosted" I believe.
> Obviously GDB requires the latterm but I can see people wanting to
> support the former for gdbserver.
There's actually some further differences. I believe - but this is
basically hearsay since I can't remember the specifics - that there
are some vendor compilers on the commercial Unices which support all
of the language features of ISO C90 but not all the runtime features.
So e.g. prototypes are fine but printf might return bogus values, to
use an example that recently bit GCC.
Anyway, I agree. We can get away with it now. If we encounter any
specific holes, I've been watching gnulib mature to fill them - I
still hope I can use their printf implementation for GDB soon.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-30 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 15:07 Denis PILAT
2007-03-29 15:12 ` Daniel Jacobowitz
2007-03-29 15:25 ` Denis PILAT
2007-03-29 17:41 ` Mark Kettenis
2007-03-29 17:48 ` Daniel Jacobowitz
2007-03-30 12:01 ` Eli Zaretskii
2007-03-30 12:12 ` Daniel Jacobowitz
2007-03-30 12:23 ` Eli Zaretskii
2007-03-30 12:23 ` Eli Zaretskii
2007-03-30 12:58 ` Daniel Jacobowitz
2007-03-30 18:53 ` Mark Kettenis
2007-03-30 19:01 ` Daniel Jacobowitz [this message]
2007-03-30 21:04 ` Jim Blandy
2007-03-30 21:13 ` Daniel Jacobowitz
2007-03-29 20:37 ` Pedro Alves
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=20070330190106.GA28397@caradoc.them.org \
--to=drow@false.org \
--cc=denis.pilat@st.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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