From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4CE8DA00C5; Tue, 21 Jun 2022 14:38:29 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3C6774069C; Tue, 21 Jun 2022 14:38:29 +0200 (CEST) Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) by mails.dpdk.org (Postfix) with ESMTP id 076B840151 for ; Tue, 21 Jun 2022 14:38:28 +0200 (CEST) Received: by mail-lj1-f176.google.com with SMTP id b23so6699783ljh.7 for ; Tue, 21 Jun 2022 05:38:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UgYk4A++x4EQdby+Z2YsoAdV8Peln+wGIJVIfg/sBrY=; b=X/sdRu1IQH8M3Q6EQSaak1ILrASV/lYt9KK+TDN0N23JEH7R5Hpjl/ev1NCKXiyPts Dv0v2QIo4Bvp+apkChk84rsQMksuM2z6sdeti+k2DlvJBASGoRJJx66emRXl+GL/i5F4 o9TEKomFshUv1vzcTBCe1+P9XQ+6QzUOlGj6WW9UJeUBq/pDW/fEodZnjgzUEQ3qUSjC /zZFFMq5AUlZMybTa7fm0FtWQNQSO3pudUsq+hJuTLMG5kIs3NRXgapDJttxIXVOvOU4 cVuajiVKb75P5NH+Jp09NcXWgQ1ZZWqflNQ9Vcu1qBlFvyv35Sli0k/xqHo7NtEpTbDq Ntfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UgYk4A++x4EQdby+Z2YsoAdV8Peln+wGIJVIfg/sBrY=; b=eahFU0OmU1ove0n41361jAaOC9M8zesPKFOuMqUgM7rLus0VElLDsTgPN9MD+unB1i dMJ111zAd7qDP0xtmXic35TKsbiNFNgA53UlPDhc7Hts3yiRE7Ip8tKYI3pW8AYVtCEa 4C2RP3wto0TR0OG0wSBp0yAhmiUwFipIYp7ikX31v/xTbP7kOt99oRGREOjxdp0CGKFe n1rF0DEUsXFYtaIyRB7nuSG57w2WCE1GqjXZdPrlxigPXnRsdwtorAulTtC9gSuRPo+2 2rIL8y8b74m4O19XSSR4Ftl15Md472wiFrffVRTgt76N058TJekOy1CGhHQlYrJCpuon IE2g== X-Gm-Message-State: AJIora/tPG5xAdt1mH0Qdmb99/LP7wKuP2B+EjEcSjrCbviDeW616jI5 n3LaZrx8L/oZtYu29PDX5/7RkgRvjA25sAjLuZspGA== X-Google-Smtp-Source: AGRyM1siUmip7SwxYbdNUXK4qk12cMeGkfzdaFxLiFjr06zqbEeaAWAEQw0k9BjP9Ix7OjxxbDco+7N6B/KZenZsLGc= X-Received: by 2002:a05:651c:1994:b0:255:aaa3:d02 with SMTP id bx20-20020a05651c199400b00255aaa30d02mr14129211ljb.410.1655815107583; Tue, 21 Jun 2022 05:38:27 -0700 (PDT) MIME-Version: 1.0 References: <20220609121701.716299-1-kda@semihalf.com> <4127934.SvYEEZNnvj@thomas> <3457544.ZfL8zNpBrT@thomas> In-Reply-To: <3457544.ZfL8zNpBrT@thomas> From: =?UTF-8?Q?Stanis=C5=82aw_Kardach?= Date: Tue, 21 Jun 2022 14:37:51 +0200 Message-ID: Subject: Re: [PATCH 0/3] Fix xmm_t to rte_xmm_t scalar conversion To: Thomas Monjalon Cc: Bruce Richardson , David Christensen , David Marchand , dev , upstream@semihalf.com, Aaron Conole , "Ananyev, Konstantin" , "Ruifeng Wang (Arm Technology China)" , Jerin Jacob Kollanukkaran Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Tue, Jun 21, 2022 at 1:53 PM Thomas Monjalon wrote: > > If it is made intentionally hard, it is just a wrong design. > A toolchain prefix is just a name. > We can have 2 toolchains compiled with the same name and different behaviours. > And we can have 2 similar toolchains with a different name. I don't think meson will allow it anytime soon (see [1]). The reasoning being that it's easy to screw up the environment and not notice it where as files are persistent. > > > So should the direction be environment or rather separating > > cross-files into arch-part and toolchain-parts and letting user create > > his own toolchain part while maintaining a matrix of supported > > combinations for CI? I'm not advocating either, just want to wrap my > > head around it. > > We should be able to use a toolchain compiled anywhere > without modifying the cross files, just because a "-gnu-" is missing > or any other irrelevant detail. I've checked that if I remove the binaries from a cross-file, then specifying CC/CXX/AR/STRIP environment variables is picked up by meson: AR=riscv64-unknown-linux-gnu-ar \ STRIP=riscv64-unknown-linux-gnu-strip \ CC=riscv64-unknown-linux-gnu-gcc \ CXX=riscv64-unknown-linux-gnu-g++ \ meson build-rv-test --cross-file=config/riscv/riscv64_linux_gcc But then there are no default values. A suggested frankenstein-like solution in [1] is to use a script that generates a cross-file with [constants] section and launches meson with it. [1] https://github.com/mesonbuild/meson/issues/9#issuecomment-381410972