public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110934] m68k: ICE with -fzero-call-used-regs=all compiling openssh 9.3p2 Date: Fri, 19 Jan 2024 23:24:22 +0000 [thread overview] Message-ID: <bug-110934-4-lIxncnc6uI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110934-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110934 --- Comment #13 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jeff Law <law@gcc.gnu.org>: https://gcc.gnu.org/g:f1dea0fed946ba40bd6bbe40ad1386aa9303418c commit r14-8299-gf1dea0fed946ba40bd6bbe40ad1386aa9303418c Author: Mikael Pettersson <mikpelinux@gmail.com> Date: Fri Jan 19 16:23:34 2024 -0700 [PATCH] Avoid ICE on m68k -fzero-call-used-regs -fpic [PR110934] PR110934 is a problem on m68k where -fzero-call-used-regs -fpic ICEs when clearing an FP register. The generic code generates an XFmode move of zero to that register, which becomes an XFmode load from initialized data, which due to -fpic uses a non-constant address, which the backend rejects. The zero-call-used-regs pass runs very late, after register allocation and frame layout, and at that point we can't allow new uses of the PIC register or new pseudos. To clear an FP register on m68k it's enough to do the move in SFmode, but the generic code can't be told to do that, so this patch updates m68k to use its own TARGET_ZERO_CALL_USED_REGS. Bootstrapped and regression tested on m68k-linux-gnu. Ok for master? (I don't have commit rights.) gcc/ PR target/110934 * config/m68k/m68k.cc (m68k_zero_call_used_regs): New function. (TARGET_ZERO_CALL_USED_REGS): Define. gcc/testsuite/ PR target/110934 * gcc.target/m68k/pr110934.c: New test.
next prev parent reply other threads:[~2024-01-19 23:24 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-07 11:33 [Bug c/110934] New: " wbx at openadk dot org 2023-08-07 12:03 ` [Bug rtl-optimization/110934] " rguenth at gcc dot gnu.org 2023-08-07 12:07 ` wbx at openadk dot org 2023-08-07 12:07 ` wbx at openadk dot org 2023-08-07 14:52 ` [Bug target/110934] " pinskia at gcc dot gnu.org 2023-08-07 16:41 ` mikpelinux at gmail dot com 2023-12-20 3:40 ` sjames at gcc dot gnu.org 2023-12-27 22:15 ` mikpelinux at gmail dot com 2023-12-28 13:44 ` mikpelinux at gmail dot com 2023-12-28 17:38 ` mikpelinux at gmail dot com 2023-12-28 18:01 ` mikpelinux at gmail dot com 2023-12-28 20:39 ` pinskia at gcc dot gnu.org 2024-01-04 16:13 ` mikpelinux at gmail dot com 2024-01-18 16:43 ` mikpelinux at gmail dot com 2024-01-19 23:24 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-19 23:25 ` law at gcc dot gnu.org 2024-01-25 6:24 ` sjames at gcc dot gnu.org 2024-03-16 0:09 ` pinskia at gcc dot gnu.org 2024-03-25 13:26 ` sjames 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-110934-4-lIxncnc6uI@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).