From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27975 invoked by alias); 15 Dec 2004 21:58:53 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 27480 invoked from network); 15 Dec 2004 21:58:39 -0000 Received: from unknown (HELO dair.pair.com) (209.68.1.49) by sourceware.org with SMTP; 15 Dec 2004 21:58:39 -0000 Received: (qmail 38571 invoked by uid 20157); 15 Dec 2004 21:58:39 -0000 Date: Wed, 15 Dec 2004 21:58:00 -0000 From: Hans-Peter Nilsson X-X-Sender: hp@dair.pair.com To: "E. Weddington" cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org Subject: Re: Revised release criteria for GCC 4.0 In-Reply-To: <41C08F48.1010205@evcohs.com> Message-ID: References: <41BDBF67.9000707@develer.com> <41C06D6B.6050905@evcohs.com> <41C08F48.1010205@evcohs.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004-12/txt/msg00624.txt.bz2 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 and GGEN > , 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