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: Kazu Hirata <kazu at cs dot umass dot edu>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Thu, 2 Oct 2003 08:27:41 -0400 (EDT)
- Subject: Re: [patch] arch-status.html: New. (Take 4)
On Wed, 1 Oct 2003, Kazu Hirata wrote:
> > easier to read if common or preferred case was blank and the
> > problematic characteristics had the character
>
> Well, I would say "less common" instead of "problematic" because there
> are two different arguments for and against cc0 for example.
>
> Anyway, I also think your version may be easier to read. What do
> others feel about this?
I agree: it's easier if the less common case uses the letter and
the common case uses a blank.
I'm not sure of the best way to cooperate with
simtest-howto.html. One way is that assuming this table goes in
a page by itself, the table from simtest-howto.html could be
removed, leaving just the checkout and build-instructions. It
would need to be referenced from the new page, but then the new
page would also have to provide build-triplet and simulator
config name for each target. Actually in some cases it'd have
to be a *couple* of targets for each arch, for example mips-elf
and mipsisa64-elf (is there a sparc64 simulator?). That would
probably bloat the new page.
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.)
brgds, H-P