From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2568 invoked by alias); 26 Nov 2013 17:38:41 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 2553 invoked by uid 89); 26 Nov 2013 17:38:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: eggs.gnu.org Received: from Unknown (HELO eggs.gnu.org) (208.118.235.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 26 Nov 2013 17:38:40 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VlMah-00041S-8h for gcc@gcc.gnu.org; Tue, 26 Nov 2013 12:38:32 -0500 Received: from oarmail.oarcorp.com ([67.63.146.244]:25914) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlMag-000415-NZ for gcc@gcc.gnu.org; Tue, 26 Nov 2013 12:38:27 -0500 Received: from [192.168.1.162] (192.168.1.162) by OARmail.OARCORP.com (192.168.2.2) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 26 Nov 2013 11:36:42 -0600 Message-ID: <5294DC85.4030700@oarcorp.com> Date: Tue, 26 Nov 2013 17:38:00 -0000 From: Joel Sherrill User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: "Joseph S. Myers" , Jan-Benedict Glaw CC: Joern Rennecke , "gcc@gcc.gnu.org" , Michael Eager Subject: Re: [buildrobot] microblaze-elf / microblaze-linux References: <1djbjk1n62mkaiqxbjm4lo51.1385469317186@email.android.com> <20131126145119.GQ30563@lug-owl.de> <20131126152755.GR30563@lug-owl.de> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: Windows XP X-Received-From: 67.63.146.244 X-IsSubscribed: yes X-SW-Source: 2013-11/txt/msg00547.txt.bz2 On 11/26/2013 10:52 AM, Joseph S. Myers wrote: > On Tue, 26 Nov 2013, Jan-Benedict Glaw wrote: > >>> The idea if config-list.mk is not to build every conceivable target >>> configuration, but to give a reasonable converage of the different >>> target architectures and OS/library configurations so that you can >>> effectively test a patch with unknown target-specific impact. >> >> Is it like that? My impression is/was that people collected a list of >> targets they somewhat care for. With around 200 configurations, among >> them some that are quite similar, adding another just adds 1/2%, which >> I'd call neglectible. > > For example, the list should include at least one target for every target > header in GCC. So if there's a header specific to an (architecture, OS) > pair, a matching configuration should be included. > It is true that the RTEMS configurations are generally similar to the *-elf ones. However, we turn on pthreads support in C++ and multitasking in the languages which have it including Ada. We have good test results even in FORTRAN. With tasking and filesystem support on near bare metal, *-rtems can potentially be used to test a lot more than *-elf. For the basic code generation, there likely isn't much difference. I often can reproduce our code generation problems using *-elf. But we have different code and more code. The key to seeing the value of testing *-rtems is moving beyond "builds or not" and into running tests on more languages. as to Joern's question: > Is there something that microblaze-rtems exposes that is not already > covered by other microblaze or rtems targets that are already included? I believe it was on the microblaze where someone broke the libgcc pattern for rtems by changing the pattern from XXX*-*-* to XXX*-*-elf. Plus we do have at least one OS/Target specific file for each *-rtems configuration. There is at least a config/*/*rtems*.h and often a config/*/t-* which is specific to RTEMS. Plus config/*rtems* is used in all *-rtems targets. -- Joel Sherrill, Ph.D. Director of Research & Development joel.sherrill@OARcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985