From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-154059-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 15720 invoked by alias); 16 May 2009 14:45:49 -0000
Received: (qmail 15447 invoked by uid 22791); 16 May 2009 14:45:48 -0000
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 	tests=AWL,BAYES_00,J_CHICKENPOX_23,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 16 May 2009 14:45:42 +0000
Received: from spaceape14.eur.corp.google.com (spaceape14.eur.corp.google.com [172.28.16.148]) 	by smtp-out.google.com with ESMTP id n4GEjdSx031200 	for <gcc@gcc.gnu.org>; Sat, 16 May 2009 15:45:39 +0100
Received: from bwz19 (bwz19.prod.google.com [10.188.26.19]) 	by spaceape14.eur.corp.google.com with ESMTP id n4GEjc2r015941 	for <gcc@gcc.gnu.org>; Sat, 16 May 2009 07:45:38 -0700
Received: by bwz19 with SMTP id 19so2410300bwz.12         for <gcc@gcc.gnu.org>; Sat, 16 May 2009 07:45:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.117.201 with SMTP id s9mr4535203bkq.36.1242485137983; Sat,  	16 May 2009 07:45:37 -0700 (PDT)
Date: Sat, 16 May 2009 20:09:00 -0000
Message-ID: <b798aad50905160745s6d5a3dcbh1d05ff9713179f75@mail.gmail.com>
Subject: [lto] Enabling LTO in selected testsuite directories
From: Diego Novillo <dnovillo@google.com>
To: Janis Johnson <janis187@us.ibm.com>, gcc@gcc.gnu.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-System-Of-Record: true
X-IsSubscribed: yes
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
X-SW-Source: 2009-05/txt/msg00426.txt.bz2

On the LTO branch, I am brute-forcing LTO compilation on all the
testsuite directories.  This causes many spurious failures because we
are not going to support LTO compiles on everything.  For instance,
LTO is not supported for fortran, java, ada, mudflap.  Also, for some
tests like pch, the tests fail trivially because of assembly
miscomparison (due to the LTO sections).

I am trying to come up with a generic mechanism that can be used in
individual .exp files so they can decide whether to test the two LTO
modes.  In terms of dg.exp, it would mean adding 3 or 4 new entries to
DG_TORTURE_OPTIONS ({-O0 -flto}, {-O2 -flto}, {-O0 -fwhopr}, {-O2
-fwhopr}).

Do you have any suggestion on how I could implement that?


Thanks.  Diego.