public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/99372] New: gimplefe-28.c ICEs when sqrt insn is not available Date: Wed, 03 Mar 2021 19:44:13 +0000 [thread overview] Message-ID: <bug-99372-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99372 Bug ID: 99372 Summary: gimplefe-28.c ICEs when sqrt insn is not available Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: aoliva at gcc dot gnu.org Target Milestone: --- Try to compile gimplefe-28.c from the testsuite with -mno-powerpc-gpopt or -msoft-float on a powerpc target, and it will ICE, because it doesn't check for the availability of the .SQRT instrinsic explicitly called in the test. Fixes for the See-Also bugs are likely to prevent the bug from showing up in test results.
next reply other threads:[~2021-03-03 19:44 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-03 19:44 aoliva at gcc dot gnu.org [this message] 2021-03-04 8:35 ` [Bug target/99372] " rguenth at gcc dot gnu.org 2021-03-10 5:00 ` aoliva 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-99372-4@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: linkBe 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).