From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124851 invoked by alias); 16 Sep 2015 14:50:43 -0000 Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org Received: (qmail 124842 invoked by uid 89); 16 Sep 2015 14:50:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mail.anw.at Received: from ns1.anw.at (HELO mail.anw.at) (195.234.101.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 16 Sep 2015 14:50:41 +0000 Received: from [10.12.40.38] ([195.29.66.214]) by mail.anw.at (8.14.4/8.14.4/Debian-4) with ESMTP id t8GEoax9023158; Wed, 16 Sep 2015 16:50:36 +0200 Message-ID: <55F981BC.1080409@anw.at> Date: Wed, 16 Sep 2015 14:50:00 -0000 From: "Jasmin J." User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Jean-Marie Lemetayer CC: Bryan Hundven , crossgcc Subject: Re: [RFC] Refactor autoconf options and build scripts References: <20150912200305.69b80a14@free-electrons.com> <55F60487.5030805@anw.at> <55F6081F.8070905@anw.at> <55F61553.6040401@anw.at> <55F82DB2.80306@gmail.com> <55F863B8.402@anw.at> <55F89FDA.5000209@anw.at> <55F96C80.9000601@anw.at> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-09/txt/msg00056.txt.bz2 Jean-Marie, > This way we can quickly identify regression on standard samples with > travis, and run full regression test when developing / reworking some > major features. I see the problem, that the samples doesn't define a gcc/binutils/... version. So the tests are done with the default (newest) versions of the tools. If we go the direction samples, then we should define the most important configurations for older GCC versions, too. I don't know which combination(s) would be representative. This is something Bryan can do best, I think. Maybe we don't need to define this combinations within the samples. We can define this in the travis-ci configuration, I guess. If you look here: http://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix -> Explicity Including Builds Can be used to define an additional env: for the GCC/binutils/... version. > This way we can quickly identify regression on standard samples with > travis, and run full regression test when developing / reworking some > major features. I agree! > If, it is OK for you, I can finish the travis part. I just need to > identify the "standard" samples. >From my point you have the "OK". It is better to start with a few tests, than nothing (like now). When someone of us has time, we can add more (GCC/binutils/... version). BR Jasmin -- For unsubscribe information see http://sourceware.org/lists.html#faq