From: Kazu Hirata <kazu@cs.umass.edu>
To: gerald@pfeifer.com
Cc: gcc@gcc.gnu.org
Subject: Re: Documenting GCC-only ABI
Date: Sun, 18 Jan 2004 22:52:00 -0000 [thread overview]
Message-ID: <20040118.175215.78709745.kazu@cs.umass.edu> (raw)
In-Reply-To: <Pine.BSF.4.58.0401182320170.40516@acrux.dbai.tuwien.ac.at>
Hi Gerald,
> > AFAIK, H8 port of GCC uses a unique ABI that no other H8 compiler
> > vendor follows. As such, it's natural to put an ABI document in some
> > place associated with GCC like gcc-x.x.x.tar.gz or http://gcc.gnu.org.
> > Any suggestions?
>
> How large is this document? One option would be adding it somewhere under
> http://gcc.gnu.org/projects, another to add a new document under gcc/doc.
Less than 150 lines so far. :-) I'll post a patch to create a new web
page then. Would a link from readings.html be OK?
Kazu Hirata
next prev parent reply other threads:[~2004-01-18 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 18:43 Kazu Hirata
2004-01-18 22:22 ` Gerald Pfeifer
2004-01-18 22:52 ` Kazu Hirata [this message]
2004-01-18 22:55 ` Gerald Pfeifer
2004-01-18 23:07 ` Joseph S. Myers
2004-01-19 5:31 ` Kazu Hirata
2004-01-19 10:54 ` Joseph S. Myers
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=20040118.175215.78709745.kazu@cs.umass.edu \
--to=kazu@cs.umass.edu \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.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).