From: Richard Biener <richard.guenther@gmail.com>
To: Paul Iannetta <piannetta@kalrayinc.com>
Cc: gcc@gcc.gnu.org
Subject: Re: LTO apparently does not support _FloatNx types
Date: Thu, 12 Jan 2023 17:35:35 +0100 [thread overview]
Message-ID: <1A99F794-8199-4235-A9DC-761C898B0470@gmail.com> (raw)
In-Reply-To: <20230112161216.d6gnsltu4izgelbm@ws2202.lin.mbt.kalray.eu>
> Am 12.01.2023 um 17:18 schrieb Paul Iannetta via Gcc <gcc@gcc.gnu.org>:
>
> 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.
> Cheers,
> Paul
>
>
>
>
next prev parent reply other threads:[~2023-01-12 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 16:12 Paul Iannetta
2023-01-12 16:35 ` Richard Biener [this message]
2023-01-13 7:15 ` Richard Biener
2023-01-13 8:15 ` Paul Iannetta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1A99F794-8199-4235-A9DC-761C898B0470@gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=piannetta@kalrayinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).