Received: by 2002:a05:6358:53a8:b0:117:f937:c515 with SMTP id z40csp2624707rwe; Sun, 16 Apr 2023 01:44:38 -0700 (PDT) X-Google-Smtp-Source: AKy350bQZpJC27jE6Sa3Ovp6VbH8CWJBfzolKupF8YQTZHqZxiNrEU+ZqB2mBUcAn/8PbbGhLcAn X-Received: by 2002:a17:902:da8e:b0:1a6:6b7d:722c with SMTP id j14-20020a170902da8e00b001a66b7d722cmr10757512plx.28.1681634677936; Sun, 16 Apr 2023 01:44:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681634677; cv=none; d=google.com; s=arc-20160816; b=ILob5NXd84LE51PCM6hpK+gEsjpF+VUYirJVKgBg03+TB8qPt7A1hxwTuyryKEC2I0 MXmFkyWyuNbqrHkdByRiib/3oULYUvSdph2T+o7FGoY7r+L6EMG7hYmmVPbhOOEA18Kh NQgvNiIl55BTnSt2ZmIy8E8JP1K7Rt8yUNji6d+w7rT1OUl/r/SEUIQlqNc2aoGMTDez 5pf0IZmsauRTpIZz77di8cUdUdaxG2wFnBNpZGNoGfKWs+iAGGwEz2Dm8RezMcQP8q8w pBLmlOR69ltkdExynWe84wjH7FerxbFNQlOu+GnWA4xOggKsbWXbWa3fMUFK/4PboIxD lYLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=HFK+NU3CJiJTWdahZrvqJWf65g/Un1VDif5WWtIXhrU=; b=r1L2NSsBG1SzuNdRsEouBVo6/+S/MSMYiQ5kWLj2OFNxiHg903UqLpKcDFe1oeWg7i CflmDgq6xmpf9fFkbcP5EOQpb0LRi/pccjMzWml3qVeAOw7z0eAJTEhxAD3ztsZ1uetz J6MlLVaQIzmkUfuja38xr05UKw3lSmqHL1efb1GQ+zys8PC9uIhbYYBtiN2Evu5rYGWv Rfpnbph3/d15HvOJbBNO9Bm4KsPup7iTgdtl3zlq9JTkpJFOrSbVKx9bLnTr/hht5oYz Jw8iJ4P0vyIhrt1OatrBzPMnv1qT+pbkwcmMgtcGiaD3yjgp1ooXmSepkkzV6sdCS6RR JduA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x6-20020a1709028ec600b0019a9834bb23si8870125plo.192.2023.04.16.01.44.24; Sun, 16 Apr 2023 01:44:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230346AbjDPIhB (ORCPT + 99 others); Sun, 16 Apr 2023 04:37:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52764 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229849AbjDPIhA (ORCPT ); Sun, 16 Apr 2023 04:37:00 -0400 Received: from 1wt.eu (ded1.1wt.eu [163.172.96.212]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 8BFC32D59 for ; Sun, 16 Apr 2023 01:36:58 -0700 (PDT) Received: (from willy@localhost) by mail.home.local (8.17.1/8.17.1/Submit) id 33G8aakP023010; Sun, 16 Apr 2023 10:36:36 +0200 Date: Sun, 16 Apr 2023 10:36:36 +0200 From: Willy Tarreau To: Borislav Petkov Cc: Jingbo Xu , tglx@linutronix.de, mingo@redhat.com, dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, "linux-kernel@vger.kernel.org" Subject: Re: [BUG REPORT] arch/x86/include/asm/uaccess_64.h:119: Error: junk at end of line Message-ID: References: <20230314102316.GAZBBLFHKqQr9RSeM+@fat_crate.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Boris, On Sat, Apr 15, 2023 at 08:56:47PM +0200, Borislav Petkov wrote: > On April 15, 2023 7:56:01 PM GMT+02:00, Willy Tarreau wrote: > >May I send you a cleaner patch for this ? > > Can you pls first send a minimal reproducer so that we can show it to gcc folks? Oh it's not even gcc, it's really just a matter of compatibility with binutils. Documentation/Changes says binutils minimum is 2.25. This toolchain I'm using in distcc was made against 2.27, I'm reproducing the error with it: $ cat repro.s .4byte (1U) .4byte (1UL) $ /f/tc/x86_64-gcc75_glibc228-linux-gnu/bin/x86_64-gcc75_glibc228-linux-gnu-ld -v GNU ld (crosstool-NG 1.24.0.500_645889f) 2.27 $ /f/tc/x86_64-gcc75_glibc228-linux-gnu/bin/x86_64-gcc75_glibc228-linux-gnu-as repro.s repro.s: Assembler messages: repro.s:2: Error: found 'L', expected: ')' repro.s:2: Error: junk at end of line, first unrecognized character is `L' This other one relying on 2.26 fails both on 1U and 1UL: $ ld -v GNU ld version 2.26.20160125 $ as repro.s repro.s: Assembler messages: repro.s:1: Error: missing ')' repro.s:1: Error: junk at end of line, first unrecognized character is `U' repro.s:2: Error: missing ')' repro.s:2: Error: junk at end of line, first unrecognized character is `U' And this one based on 2.29 works for both: $ /dev/shm/gcc-5.5.0-nolibc/x86_64-linux/bin/x86_64-linux-ld -v GNU ld (GNU Binutils) 2.29.1.20170915 $ /dev/shm/gcc-5.5.0-nolibc/x86_64-linux/bin/x86_64-linux-as repro.s So it just means that the support for the "U" suffix on numbers was added in binutils 2.27 and the "L" suffix on numbers was added somewhere between 2.27 and 2.29. And given that there's a single occurrence of all this in the whole tree, that's why I'm proposing to just get back to the good old (1 << 0) instead of BIT(0). Thanks! Willy