This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] arch-status.html: New. (Take 4)
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Janis Johnson <janis187 at us dot ibm dot com>
- Cc: Kazu Hirata <kazu at cs dot umass dot edu>, <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 2 Oct 2003 15:47:04 -0400 (EDT)
- Subject: Re: [patch] arch-status.html: New. (Take 4)
On Thu, 2 Oct 2003, Janis Johnson wrote:
> On Thu, Oct 02, 2003 at 08:27:41AM -0400, Hans-Peter Nilsson wrote:
> > Alternatively, we could leave simtest-howto.html mostly as is
> > but remove some of the trivial arch-related comments and add
> > references from simtest-howto.html to the new page for the
> > removed arch info. The new page would reference
> > simtest-howto.html for arches with targets that have simulator
> > build instructions. (Ah, this one gets my vote.)
>
> The table in simtest-howto.html could show the triples used for builds
> and also the architecture name that is used in the new file
> (backends.html?), with a link to the new file.
Yeah. Often the archname is the same as the first triplet part,
but not always. I was thinking a link directly to the arch
entry on the new page, but it wouldn't be much of a point if
it's (hopefully) a short page.
> The new file could
> mention in one place (i.e., not in the table)
I kind of liked the idea of a cross-reference from the table,
(perhaps from the snap-in-simulator letter!) but I'm ok either
way.
> that targets that have
> simulators can be tested via the instructions in simtest-howto.html.
Actually, only targets that have simulators which have
snap-in-support through dejagnu and a newlib (or a similarly
simple snap-in library) configuration. Most of the simulators
people mentioned do not AFAIK, but it'd certainly be doable and
worthwhile for GCC maintenance!
brgds, H-P