From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3C7C7A0524; Fri, 27 Nov 2020 09:39:24 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 805CCC938; Fri, 27 Nov 2020 09:39:22 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by dpdk.org (Postfix) with ESMTP id 97A6EC92A for ; Fri, 27 Nov 2020 09:39:19 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606466358; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=mVvSch2yZf+ofPBFFTfH18aPo2qIAgAzBOgd7/MmDiE=; b=N3FmNT9yf6wZZmDp49nlD6PDTEF5PFbk07nwPkZbObxMLkYVivuBvJEk/193BWB2SGAEH4 iWyPWD5o360yqPXsK9cct7Pxnfu/LBnsA3JrBokoObIO5ZnQPtd7qWvoc7nWTzzfrDF9NY eQFu4eqZmvjbtnOwRAfNz1ROq5A5rTo= Received: from mail-vk1-f198.google.com (mail-vk1-f198.google.com [209.85.221.198]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-419-Bl4DQLukM9WPzDiXVpspjQ-1; Fri, 27 Nov 2020 03:39:16 -0500 X-MC-Unique: Bl4DQLukM9WPzDiXVpspjQ-1 Received: by mail-vk1-f198.google.com with SMTP id g199so1467607vke.13 for ; Fri, 27 Nov 2020 00:39:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mVvSch2yZf+ofPBFFTfH18aPo2qIAgAzBOgd7/MmDiE=; b=XSusbg9m2pNpsTOpj+CUVMyVQOny0XEradzOQ3V37RDgMSNbXGyTme66VmMngCa9df J2nSRInZC5hT3gfDQg7Jdf+JYugXqs/2ZG2Xyv4dfBQPRYgQB0femiwPJjvmMgulACKy SOP1JEV4JbP8JT/dJV0EvDgHDxAovLllulzBh0wzP3yrAh5Cog24/nFlQ8qBkFZS1Sgo 0SU2DRu9127hhq/r9MCvTiNbDY0WcnNxKrN68PyUcBBpcYBSJ4bU5lC+rk8ppnEQllxc xuHXluMAIl0j9X9UihucvmTA3m4eMGO91oEPYRqojKbizJ6c30tTKPxM3h7OWiMvy7Dg qWmA== X-Gm-Message-State: AOAM5314yGzoT3O6eOmXstH6d7MyMHDSwnmuXexWGirOD10aCeU5GqqT uwRqLopR4/NZEDiGkCWrvnPUWxZOwXbso/IYsgejCBG/bcjDL4RSJamCK2wIp+4JsqWx5VqRZGG 8Wg7Qm8ACvONo3D/W3JA= X-Received: by 2002:a67:f613:: with SMTP id k19mr4405568vso.17.1606466356024; Fri, 27 Nov 2020 00:39:16 -0800 (PST) X-Google-Smtp-Source: ABdhPJwvx0zHHNnA66YjXP5+W0HX/iHaeyqW7xm0UkzjbgmeZrIo6epVU05HdHCiXyQIIms/PxPGJFS2oFDk3M+InxU= X-Received: by 2002:a67:f613:: with SMTP id k19mr4405557vso.17.1606466355866; Fri, 27 Nov 2020 00:39:15 -0800 (PST) MIME-Version: 1.0 References: <20201127080903.26817-1-ruifeng.wang@arm.com> <20201127080903.26817-2-ruifeng.wang@arm.com> In-Reply-To: <20201127080903.26817-2-ruifeng.wang@arm.com> From: David Marchand Date: Fri, 27 Nov 2020 09:39:05 +0100 Message-ID: To: Ruifeng Wang , Jerin Jacob Cc: Honnappa Nagarahalli , dev , nd , Feifei Wang Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH 1/2] eal/arm: fix gcc build for optimization level 0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Nov 27, 2020 at 9:10 AM Ruifeng Wang wrote: > > Gcc build with '-O0' on platforms with RTE_ARM_FEATURE_ATOMICS set > failed for: > ../lib/librte_efd/rte_efd.c > Assembler messages: > 3866: Error: selected processor does not support `crc32cb w0,w0,w1' > 3890: Error: selected processor does not support `crc32ch w0,w0,w1' > 3914: Error: selected processor does not support `crc32cw w0,w0,w1' > 3938: Error: selected processor does not support `crc32cx w0,w0,x1' > > This was caused by an architecture specifier added for Clang. > Unlike Clang, Gcc considers each inline assembly block to be dependent > and therefor, the architecture specifier impacts assemble of some > blocks require certain extension support. I reproduced this error with -O0 for config/arm/arm64_octeontx2_linux_gcc. The patch looks simple enough and it only affects ARM builds. Jerin, Are you okay with this change for 20.11? Or should we wait 21.02? Ruifeng, Looking at the kernel, I see no distinction with gcc/clang, so I'd say the kernel has the same issue, or is there something else that differs in dpdk? Besides, the kernel patch previously mentioned had a followup fix. -- David Marchand