From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fx403.security-mail.net (smtpout140.security-mail.net [85.31.212.143]) by sourceware.org (Postfix) with ESMTPS id 74C023858D32 for ; Fri, 13 Jan 2023 08:15:30 +0000 (GMT) Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=kalray.eu Received: from localhost (localhost [127.0.0.1]) by fx403.security-mail.net (Postfix) with ESMTP id 354C82718FC for ; Fri, 13 Jan 2023 09:15:28 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kalrayinc.com; s=sec-sig-email; t=1673597728; bh=Pwh+Ui2YNdGQ5vEimdoV1lP9xNrILjBS2dGMHnhcI7g=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=FFyvHRdm4QsUjfurIovHHcu50N/QfPS1BGveWJHtBLpZUxn0QGBhOWsXXKzpDiFRj 8YFzJIKk4nu6lFjTR0zK1qOUvR1GBBCMnog3gqEHUq/ZoYJbUf90ggEJGDRGKWs9g7 S2VtiLFzy/LCDea4kK1f+lPDYse5Cl3WX81WSCGM= Received: from fx403 (localhost [127.0.0.1]) by fx403.security-mail.net (Postfix) with ESMTP id 1BED52721A4; Fri, 13 Jan 2023 09:15:28 +0100 (CET) Received: from zimbra2.kalray.eu (unknown [217.181.231.53]) by fx403.security-mail.net (Postfix) with ESMTPS id 85151271BEB; Fri, 13 Jan 2023 09:15:27 +0100 (CET) Received: from zimbra2.kalray.eu (localhost [127.0.0.1]) by zimbra2.kalray.eu (Postfix) with ESMTPS id 57DC027E03FE; Fri, 13 Jan 2023 09:15:27 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by zimbra2.kalray.eu (Postfix) with ESMTP id 3EFCE27E0418; Fri, 13 Jan 2023 09:15:27 +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 cQWsSnlRli7k; Fri, 13 Jan 2023 09:15:27 +0100 (CET) Received: from localhost (unknown [192.168.37.51]) by zimbra2.kalray.eu (Postfix) with ESMTPSA id 1F54427E03FE; Fri, 13 Jan 2023 09:15:27 +0100 (CET) X-Virus-Scanned: E-securemail Secumail-id: <13dd0.63c1131f.84000.0> DKIM-Filter: OpenDKIM Filter v2.10.3 zimbra2.kalray.eu 3EFCE27E0418 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kalrayinc.com; s=4F334102-7B72-11EB-A74E-42D0B9747555; t=1673597727; bh=8N3wCZ2uNZoBtvqERMNn8jDRNO4x5WBjzgUkNLIfh5k=; h=Date:From:To:Message-ID:MIME-Version; b=MiZDe23DhmL3z73avrHKRv9/w6Rdb9gR7cp965mhcOjCgCCEGAyShY3qd0shIGQ90 saPbc25DiOomXCph6208ypAhAAvnFt0VHb6169YpGmnpggipnjGVVrQWH1v29gFvGT HYbNkRk8XSz4bxCB7HUpXmVpQFU+hqpIaBtd3HSJaLJYKcU5NZ5kDDBilLc5ygKZ6+ fcgWjl2ukSz7G2J9OujvxW9uHVDWYpZw+bGVN/Gz3G2yopJWdhHiPve7LSod6sozwI rqbuksqwpO7uJdHyVH9EvzaRqiFQGy/Jz3X6VloduKQiZ8aqHGTkjOIFgiYey1A2ya Gb9/VIFffODgw== Date: Fri, 13 Jan 2023 09:15:26 +0100 From: Paul Iannetta To: Richard Biener Cc: gcc@gcc.gnu.org Subject: Re: LTO apparently does not support _FloatNx types Message-ID: <20230113081526.cp3ob37vmykusohn@ws2202.lin.mbt.kalray.eu> References: <20230112161216.d6gnsltu4izgelbm@ws2202.lin.mbt.kalray.eu> <1A99F794-8199-4235-A9DC-761C898B0470@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20171215 Content-Transfer-Encoding: 8bit X-ALTERMIMEV2_out: done X-Spam-Status: No, score=-5.2 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: On Fri, Jan 13, 2023 at 08:15:34AM +0100, Richard Biener wrote: > On Thu, Jan 12, 2023 at 5:35 PM Richard Biener > wrote: > > > > > > > > > Am 12.01.2023 um 17:18 schrieb Paul Iannetta via Gcc : > > > > > > 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? > > > > It’s probably an oversight. > > I'm testing a patch to sync them up. > > Richard. > Wonderful, thanks! Paul > > > > > Cheers, > > > Paul > > > > > > > > > > > > > > > >