From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-201123-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 114275 invoked by alias); 19 Dec 2019 20:50:42 -0000
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
Received: (qmail 114267 invoked by uid 89); 19 Dec 2019 20:50:42 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=H*i:sk:f0a81c0, H*f:sk:f0a81c0, check-gcc, checkgcc
X-HELO: mail-vs1-f44.google.com
Received: from mail-vs1-f44.google.com (HELO mail-vs1-f44.google.com) (209.85.217.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 19 Dec 2019 20:50:40 +0000
Received: by mail-vs1-f44.google.com with SMTP id f8so4637518vsq.8        for <gcc@gcc.gnu.org>; Thu, 19 Dec 2019 12:50:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc:content-transfer-encoding;        bh=POOwauvsVTc5GGMNbxrj2PQYLCL5o5wQ/lwDpyajVkU=;        b=iju8F6asE8urUxCLEX+uMswubKbdWb19Hx2B5wk6cJseSWUCcmd6JdSqGCb6iudVL0         Y+IGDMDQUQFVQ4HUCLbf/aWUseYR8h7BFwtU/1FSa885P5kCYW2WFoSYHbtGEBymxihE         DEN6AmppuOBvk3e/uhD0vf8lhnbjdmbr/jyDSL0OCQHuHObWLwitrdT75s/Yrfce3/dQ         +4cixDkSOKHbjq2gOJj/MUfXwbr88F/oWHDOQpKXRhbPwnLgbHXVw23+CFaqZWeCu1t9         e6ewaRWjKP/vr56dkXlmvjHU7F1FG+jdlcc0waevsL/T27eeFAhnx35UXQnBkHLgBk0d         yYzA==
MIME-Version: 1.0
References: <f0a81c04-8ce4-5c61-e1dd-316c0d64171a@theobroma-systems.com>
In-Reply-To: <f0a81c04-8ce4-5c61-e1dd-316c0d64171a@theobroma-systems.com>
From: Andrew Pinski <pinskia@gmail.com>
Date: Thu, 19 Dec 2019 20:50:00 -0000
Message-ID: <CA+=Sn1=2D6AJf8=ixumCr-STXfEVOuFbjs-9c2U0jtZmB3ediQ@mail.gmail.com>
Subject: Re: How to run LTO tests?
To: Erick Ochoa <erick.ochoa@theobroma-systems.com>
Cc: GCC Development <gcc@gcc.gnu.org>, 	=?UTF-8?Q?Christoph_M=C3=BCllner?= <christoph.muellner@theobroma-systems.com>, 	"Dr. Philipp Tomsich" <philipp.tomsich@theobroma-systems.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
X-SW-Source: 2019-12/txt/msg00341.txt.bz2

On Thu, Dec 19, 2019 at 12:48 PM Erick Ochoa
<erick.ochoa@theobroma-systems.com> wrote:
>
> Hi,
>
> I'm looking to create new tests for an LTO pass that I'm working on.
> So, I started by trying to run the tests under the folder:
> $gcc/gcc/testsuite/gcc.dg/lto
>
> Looking at the documentation available here:
> https://gcc.gnu.org/install/test.html
>
> It says the following
>
>   In order to run sets of tests selectively, there are targets
>   [...]  =E2=80=98make check-lto=E2=80=99 in the gcc subdirectory of the =
object directory.
>
> And so, I go to gcc subdirectory of the object directory and
> type make check-lto. However, I get this error message:
>
>   make: Nothing to be done for `check-lto'.
>
> I have looked into the Makefile, and there is indeed a check-lto
> target but make outputs "Nothing to be done for `check-lto'."
>
> Just to be complete, these are the configure flags I used
> when installing gcc:
>
> ../configure \
>   --disable-bootstrap \
>   --disable-libsanitizer \
>   --enable-__cxa_atexit \
>   --enable-shared \
>   --disable-libsanitizer \
>   --enable-languages=3Dc,c++,fortran \
>   --enable-lto \
>   --enable-gold \
>   --enable-linker-build-id \
>   --with-cpu-emag \
>   --prefix=3D"$HOME/code/${installdir}/"
>
> Can anyone tell me how can I run the lto tests?

Did you try:
make check-gcc RUNTESTFLAGS=3D"lto.exp" ?

Thanks,
Andrew Pinski

>
> Thanks!