This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Revised release criteria for GCC 4.0


On Wed, 15 Dec 2004, E. Weddington wrote:
> Ok, sure. But realistically, it's going to be the AVR port developers
> who will be running the testsuite, and they're already familiar with
> avr-libc (I'm excluding the RTEMS folks for this argument).

You're still missing the point that the simtest-howto.html stuff
is generally not for port maintainers but for *other* GCC
developers.

> So, from what I gather with that statment, is that using newlib is just
> a convenience; there's nothing inherent in it that is required for
> testing with a simulator?

Correct.  Of course, you need for newlib to generate and for the
simulator to have special calls for e.g. file operations and
memory allocation.

> Hmm, that's what I was hoping to find out, documentation for those types
> of simulators. I've seen SID <http://sources.redhat.com/sid/> and GGEN
> <http://sources.redhat.com/cgen/>, but does anybody know what is
> currently being used to develop those simulators in the sim directory?,
> what should be used?

If there's already an AVR simulator, you shouldn't start from
scratch; just connect it to the sim framework.  See ppc, arm or
sh simulators for instance.  No documentation, but plenty of
source code.  When starting from scratch and for gcc testing,
CGEN or igen would be better than SID, because SID needs more
than is covered by the simtest-howto.html instructions.

brgds, H-P


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]