Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp898660ybi; Fri, 21 Jun 2019 10:01:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqyUK2NfkQUVicjORdmUqjbC1Tz74rlNUUjZUCotc0IwkJAKCzbNVOP+xtVUE1Gq24V82sxN X-Received: by 2002:a17:90a:e397:: with SMTP id b23mr7824807pjz.140.1561136477929; Fri, 21 Jun 2019 10:01:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561136477; cv=none; d=google.com; s=arc-20160816; b=Ha5EDQyaHpGr64xJx+Y/WPBkE27C+9sBsVXPrkusETleG3MZ+AodsBlcf0vYAcvKCU NSBVFnAVKP0MP3XkI1p7So5NYcnK0Sp79zNBZ1aP5xeSU3EZqG9mO8VRxJuFrTqXzS7O c5z2fOP/SKNxdXgHBeJLEeDHGVlqH34x8xqw53sXAZJZ6tRFOrBeeqzsBYwkgu9eMmC4 yUkBKCoztHUBbO3cu/6HTjth3hCf67soHEfCh3yZTyzqyhpm7e94MxlwjtHWG0X4aFez 4lloIYS6okK/ahsESAcDQaDPblEQvGectbKDxrPGr07FaCliFf3SRJarqhOotW0d0c1b hEbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature:dkim-filter; bh=BdGlYHfhJn0WnD4j8rj3j0Dpi7bkUswm7gLUuW2VoBQ=; b=QsK+5KzKBv49mxwWru2gX8ql0fgKnWHcGqVWcpRO3HuZVBLZ+xJPpoya9h+PRGvEWW WO4zNUin3kwkYh9ztCCpdXsdvSofPth9mAqpdOngLtTc8vFxCu9Jo0lcpCuby34DmEgp YE6g4JICSaSDv/Rli7MsUG0667FSbBJus+4E3QIqVns5fzwRB0nas8CXkZDB8Kgtl8fj 0x2L7XWzgZFKS/9pxyxU67CaAXmHl1H90AaO9wVuz0OlTuYZvFu1wjNMeZO6k3VmuTGC OM2G87yI7fruemwmhqdxquZAA5rXlLH/vaNi/ldOIAhwcZR1yV7xiwUyP/kqI2UJkcuJ Bl9Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=1uawYuat; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t11si3107837pgn.369.2019.06.21.10.01.01; Fri, 21 Jun 2019 10:01:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=1uawYuat; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726196AbfFUQ6q (ORCPT + 99 others); Fri, 21 Jun 2019 12:58:46 -0400 Received: from conssluserg-01.nifty.com ([210.131.2.80]:30028 "EHLO conssluserg-01.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725985AbfFUQ6q (ORCPT ); Fri, 21 Jun 2019 12:58:46 -0400 Received: from mail-ua1-f51.google.com (mail-ua1-f51.google.com [209.85.222.51]) (authenticated) by conssluserg-01.nifty.com with ESMTP id x5LGwQCk013255 for ; Sat, 22 Jun 2019 01:58:27 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com x5LGwQCk013255 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1561136307; bh=BdGlYHfhJn0WnD4j8rj3j0Dpi7bkUswm7gLUuW2VoBQ=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=1uawYuatNdqEqxzcJpgQW/gvsybkA6Ru4SsyggVJAXjQslufFjMtq4AlphsSdE6Jj TPc+JfVJOQLXuhkJ3ClXJbarN6pg8Z4A2lpf3RwZM/TMT2TNakvusNat9c0Ona3zfc 2Xz+X/iepW2zl0IWoMIXlE5iF4GmJC3JHZk9jO70kDzD8PBB0iD1UJzSPA2KRwrqnF QuBVevl16he/A1o1rE2Fkjqb6sAiPcTxDFHkOanpCBIb24zVzk9Rv1H14VqD1zddyV MAhKQBjd9Bi4NyIH1ah9SsaTm+Lix+m5LcmSrAv8825JopeEm7XR6weJnbVQspCM+K /oW4Mex8JgFMA== X-Nifty-SrcIP: [209.85.222.51] Received: by mail-ua1-f51.google.com with SMTP id o19so3184076uap.13 for ; Fri, 21 Jun 2019 09:58:27 -0700 (PDT) X-Gm-Message-State: APjAAAWwuusnil8vYVFWOaJsZhHlp4FI5CHp5x1te/ELnZRMcFPH6pWJ URnbFdrBxUTGrhmsqUfzg9ffIo1jJoFGexFHsQc= X-Received: by 2002:ab0:2b0a:: with SMTP id e10mr43253033uar.109.1561136305833; Fri, 21 Jun 2019 09:58:25 -0700 (PDT) MIME-Version: 1.0 References: <20190618131048.543-1-will.deacon@arm.com> <20190618162021.GA4270@fuggles.cambridge.arm.com> In-Reply-To: <20190618162021.GA4270@fuggles.cambridge.arm.com> From: Masahiro Yamada Date: Sat, 22 Jun 2019 01:57:49 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] genksyms: Teach parser about 128-bit built-in types To: Will Deacon Cc: Arnd Bergmann , Linux Kernel Mailing List , Dave Martin , Richard Henderson , Ard Biesheuvel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 19, 2019 at 1:21 AM Will Deacon wrote: > > Hi Arnd, > > On Tue, Jun 18, 2019 at 04:17:35PM +0200, Arnd Bergmann wrote: > > On Tue, Jun 18, 2019 at 3:10 PM Will Deacon wrote: > > > > > > + { "__int128", BUILTIN_INT_KEYW }, > > > + { "__int128_t", BUILTIN_INT_KEYW }, > > > + { "__uint128_t", BUILTIN_INT_KEYW }, > > > > I wonder if it's safe to treat them as the same type, since > > __int128_t and __uint128_t differ in signedness. > > > > If someone exports a symbol with one and changes it to the other, they > > would appear to be the same type. > > My understanding is that the actual CRC generation for normal symbols is > based purely on the string-representation of the function signature, and > so the underlying type information isn't relevant to that. I can also > confirm that the CRC for an exported symbol that returns a __uint128_t > is not the same if you change it to return a __int128_t instead. Right. Applied to linux-kbuild. Thanks! -- Best Regards Masahiro Yamada