public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106279] New: reload problem on arm iwmmxt Date: Wed, 13 Jul 2022 08:01:29 +0000 [thread overview] Message-ID: <bug-106279-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106279 Bug ID: 106279 Summary: reload problem on arm iwmmxt Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- For the C testsuite file ./gcc.target/aarch64/vect_unary_1.c, compiled by an ARM cross compiler, with target arch set to iwmmxt, does this: $ /home/dcb/raspberrypi/results/bin/arm-linux-gnueabihf-gcc -c -march=iwmmxt bug827.c during RTL pass: reload ./gcc.target/aarch64/vect_unary_1.c: In function ‘test2_int_clz_int’: ./gcc.target/aarch64/vect_unary_1.c:15:1: internal compiler error: maximum number of generated reload insns per insn achieved (90) 15 | } \ | ^ ./gcc.target/aarch64/vect_unary_1.c:161:1: note: in expansion of macro ‘TEST2’ 161 | TEST2 (int, clz, int) | ^~~~~ 0xe06010 lra_constraints(bool) /home/dcb/gcc/trunk.git/gcc/lra-constraints.cc:5126 Similar things happen with target arch set to iwmmxt2.
next reply other threads:[~2022-07-13 8:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-13 8:01 dcb314 at hotmail dot com [this message] 2022-07-13 9:10 ` [Bug target/106279] " wilco at gcc dot gnu.org 2022-07-13 9:15 ` dcb314 at hotmail dot com 2022-07-13 9:17 ` wilco at gcc dot gnu.org 2022-09-01 13:01 ` rearnsha at gcc dot gnu.org 2022-09-01 13:06 ` rearnsha 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-106279-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).