From: Phil Edwards <phil@codesourcery.com>
To: Petar Penchev <ptr@melexis.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC low-level runtime library
Date: Wed, 08 Oct 2003 06:47:00 -0000 [thread overview]
Message-ID: <20031008064719.GA2895@disaster.jaj.com> (raw)
In-Reply-To: <001e01c38d64$45599290$7303230a@PTR>
On Wed, Oct 08, 2003 at 09:20:29AM +0300, Petar Penchev wrote:
> Hello All,
> I am looking for a document describing "GCC low-level runtime library" in a
> more detailed
> way than it is done in "GCC internals".
> I will be very grateful if somebody gives a link or a document :)))
The internals manual is the most detailed document there is for libgcc. If a
more detailed document existed, we would merge it into the internals manual.
--
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
- Brian W. Kernighan
next prev parent reply other threads:[~2003-10-08 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 6:18 Petar Penchev
2003-10-08 6:47 ` Phil Edwards [this message]
2003-10-08 17:27 ` Joe Buck
2003-10-09 5:00 ` [gcc] " Petar Penchev
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=20031008064719.GA2895@disaster.jaj.com \
--to=phil@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=ptr@melexis.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).