From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fx405.security-mail.net (smtpout140.security-mail.net [85.31.212.145]) by sourceware.org (Postfix) with ESMTPS id 8728E3858D35 for ; Thu, 12 Jan 2023 16:12:26 +0000 (GMT) Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=kalray.eu Received: from localhost (fx405.security-mail.net [127.0.0.1]) by fx405.security-mail.net (Postfix) with ESMTP id E33CB335EFF for ; Thu, 12 Jan 2023 17:12:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kalrayinc.com; s=sec-sig-email; t=1673539944; bh=IbN6QXSXwIYCidPgmY6JyaLtTXfsvtuSrx4RQidDT40=; h=Date:From:To:Subject; b=jB2lPnuyrSLSH/TEznEapJDifc/PyWkU9Q8D+VG8rflMpHwHNa7xbe2tW+f1Re2kd 7VydmnvTAORyf7PFZvK0KyDJdhaDvY2+Fc8s/tBQI5GdDvPCh3GRms3OHg6xmSgRIm OpkwiTZjrsAl7QRJawv3T1joeipOhYpjjT7ebZUw= Received: from fx405 (fx405.security-mail.net [127.0.0.1]) by fx405.security-mail.net (Postfix) with ESMTP id 9CFD3335ED3 for ; Thu, 12 Jan 2023 17:12:24 +0100 (CET) Received: from zimbra2.kalray.eu (unknown [217.181.231.53]) by fx405.security-mail.net (Postfix) with ESMTPS id BE18B335ED6 for ; Thu, 12 Jan 2023 17:12:23 +0100 (CET) Received: from zimbra2.kalray.eu (localhost [127.0.0.1]) by zimbra2.kalray.eu (Postfix) with ESMTPS id A4B6827E0417; Thu, 12 Jan 2023 17:12:23 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by zimbra2.kalray.eu (Postfix) with ESMTP id 8D3BF27E0418; Thu, 12 Jan 2023 17:12:23 +0100 (CET) Received: from zimbra2.kalray.eu ([127.0.0.1]) by localhost (zimbra2.kalray.eu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id P6XUEXXgDdZL; Thu, 12 Jan 2023 17:12:23 +0100 (CET) Received: from localhost (unknown [192.168.37.51]) by zimbra2.kalray.eu (Postfix) with ESMTPSA id 731D827E0417; Thu, 12 Jan 2023 17:12:23 +0100 (CET) X-Virus-Scanned: E-securemail Secumail-id: <2eb.63c03167.bc46a.0> DKIM-Filter: OpenDKIM Filter v2.10.3 zimbra2.kalray.eu 8D3BF27E0418 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kalrayinc.com; s=4F334102-7B72-11EB-A74E-42D0B9747555; t=1673539943; bh=IbN6QXSXwIYCidPgmY6JyaLtTXfsvtuSrx4RQidDT40=; h=Date:From:To:Message-ID:MIME-Version; b=TnSbrFDDCzbK/GHVNvZagpcKWGDk4ID+fc+lGqaXst2nF/fOLNkbj0g5jFEKUfOdO Ck41Z8UYlASpgfnD7Db/8GFi0FvVE+HS4kUNb28jbePZiwYOOeEQlbuKtaEqOmg0ur hgw2B+4w+RPvk3/+yXf3G2v3K5ZlBUfjlgbQ9jQpH/tVlfrqhIb+Lc1y7t4zhfMyw9 ICnXBgPGIeUMABcAliQSKFmaZsNKYERWuPFTmMHrRfdUQYeXnGYhpCb21eEAgjrYJf 4WGccvQdIBTADA9cCxftf5ZroNq/oRbpseC7PUfA/3KjAEj8iSVYZmNeL3TPG7ZQha Z5FGFBQOGnErA== Date: Thu, 12 Jan 2023 17:12:16 +0100 From: Paul Iannetta To: gcc@gcc.gnu.org Subject: LTO apparently does not support _FloatNx types Message-ID: <20230112161216.d6gnsltu4izgelbm@ws2202.lin.mbt.kalray.eu> MIME-Version: 1.0 Content-Disposition: inline User-Agent: NeoMutt/20171215 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-ALTERMIMEV2_out: done X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi, I was investigating an ICE (in our yet to be upstreamed back-end which has native support for float16), on "gcc.dg/torture/float16-complex.c" when compiled with lto: ./gcc/build/gcc/xgcc -B./gcc/build/gcc/ ./gcc/gcc/testsuite/gcc.dg/torture/float16-complex.c \ -O2 -flto -fno-use-linker-plugin -flto-partition=none -lm -o ./float16-complex.exe I narrowed it down to the fact that lto-lang does not support _FloatNx types, the function "lto_type_for_mode" (in gcc/lto/lto-lang.c) and "c_common_type_for_mode" (in gcc/c-family/c-common.c) are exactly the same except that "lto_type_for_mode" does not support _FloatNx. Is this intentional or an oversight? Cheers, Paul