public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105374] [12 Regression] ICE in fold_convert_loc, at fold-const.cc:2580 during GIMPLE pass: reassoc since r12-7338-g884f77b4222289510e1df9db2889b60c5df6fcda Date: Mon, 25 Apr 2022 13:47:51 +0000 [thread overview] Message-ID: <bug-105374-4-cp4lbQdgzs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105374-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105374 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Also, no idea where exactly to put the testcase to and what dg-* directives to use, arm testcases is something I'm really not familiar with. Perhaps gcc.target/arm/mve/general and /* { dg-do compile } */ /* { dg-require-effective-target arm_v8_1m_mve_ok } */ /* { dg-add-options arm_v8_1m_mve } */ but can -mfloat-abi=hard be just added or does it require some extra magic?
next prev parent reply other threads:[~2022-04-25 13:47 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-25 12:08 [Bug tree-optimization/105374] New: " acoplan at gcc dot gnu.org 2022-04-25 12:09 ` [Bug tree-optimization/105374] " acoplan at gcc dot gnu.org 2022-04-25 13:43 ` jakub at gcc dot gnu.org 2022-04-25 13:44 ` jakub at gcc dot gnu.org 2022-04-25 13:47 ` jakub at gcc dot gnu.org [this message] 2022-04-25 14:27 ` clyon at gcc dot gnu.org 2022-04-25 15:23 ` clyon at gcc dot gnu.org 2022-04-25 16:38 ` marxin at gcc dot gnu.org 2022-04-25 16:39 ` marxin at gcc dot gnu.org 2022-04-26 6:33 ` rguenth at gcc dot gnu.org 2022-04-26 7:58 ` cvs-commit at gcc dot gnu.org 2022-04-26 7:58 ` jakub at gcc dot gnu.org 2022-04-27 8:20 ` cvs-commit 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-105374-4-cp4lbQdgzs@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).