public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105367] [12 Regression] ICE: SIGSEGV in contains_struct_check (tree.h:3570) with -Ofast -mveclibabi=acml
Date: Mon, 25 Apr 2022 10:49:05 +0000 [thread overview]
Message-ID: <bug-105367-4-zm6HdBuAY3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105367-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105367
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #3)
> Created attachment 52864 [details]
> gcc12-pr105367-2.patch
>
> Variant patch (smaller, just i386 backend). Advantage of the first one is
> that
> we can use that elsewhere later on.
This one is certainly obvious. I'm less sure about mapping back modes to
_Float and then the corresponding library functions - can we not get into the
situation choosing 'double' for SFmode (on targets where double == float) but
the target
only having sinf() but not sin()? I guess we have to be more clever wrt
libm.libc_has_function () and choosing the function when we have multiple
choices?
next prev parent reply other threads:[~2022-04-25 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 19:00 [Bug tree-optimization/105367] New: " zsojka at seznam dot cz
2022-04-25 7:02 ` [Bug tree-optimization/105367] " rguenth at gcc dot gnu.org
2022-04-25 10:38 ` jakub at gcc dot gnu.org
2022-04-25 10:40 ` jakub at gcc dot gnu.org
2022-04-25 10:49 ` rguenth at gcc dot gnu.org [this message]
2022-04-26 7:40 ` cvs-commit at gcc dot gnu.org
2022-04-26 8:14 ` jakub at gcc dot gnu.org
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=bug-105367-4-zm6HdBuAY3@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).