From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 966 invoked by alias); 1 Nov 2007 13:32:23 -0000 Received: (qmail 957 invoked by uid 22791); 1 Nov 2007 13:32:23 -0000 X-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 01 Nov 2007 13:32:20 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.1) with ESMTP id lA1DWGq1011358; Thu, 1 Nov 2007 09:32:16 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lA1DWGHq017504; Thu, 1 Nov 2007 09:32:16 -0400 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lA1DWEaH027226; Thu, 1 Nov 2007 09:32:15 -0400 Message-ID: <4729D50B.8010302@redhat.com> Date: Thu, 01 Nov 2007 13:32:00 -0000 From: Andrew Cagney User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: Mark Wielaard CC: frysk@sourceware.org Subject: Re: Build with --disable-arch32-tests for gen-type-funit-tests References: <1193830994.3841.3.camel@dijkstra.wildebeest.org> <1193913362.11892.3.camel@dijkstra.wildebeest.org> In-Reply-To: <1193913362.11892.3.camel@dijkstra.wildebeest.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q4/txt/msg00098.txt.bz2 Mark Wielaard wrote: > This should now all be fixed by: > (I'm assuming there wasn't a bug) > Andrew, would it make sense to automatically run the arch32 tests in > make check whenever they are build? > Enabling 32-on-64 specific tests? Yes. They exercise 32-on-64 specific edge cases (the pedant will point out that when not run on a 64-bit system they should be marked as unresolved, not unsupported :-). For instance testing 64-32-64 execs. This is on my to-do list. Running test-runner twice, once in 32-bit mode and once in 64-bit mode, is something better suited for the make file. Andrew > Cheers, > > Mark >