public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sebastian.huber@embedded-brains.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/106680] Test gcc.target/powerpc/bswap64-4.c fails on 32-bit BE Date: Wed, 07 Feb 2024 14:08:43 +0000 [thread overview] Message-ID: <bug-106680-4-HcIwAFPMFW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106680-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106680 --- Comment #14 from Sebastian Huber <sebastian.huber@embedded-brains.de> --- Thanks for your help, it seems that this patch fixes the issue for RTEMS: diff --git a/gcc/config/rs6000/rtems.h b/gcc/config/rs6000/rtems.h index 57a2325991b..b36e64fec77 100644 --- a/gcc/config/rs6000/rtems.h +++ b/gcc/config/rs6000/rtems.h @@ -36,6 +36,10 @@ #endif #endif +/* RTEMS configured for the 32-bit multilibs doesn't support saving and + restoring 64-bit regs. */ +#define OS_MISSING_POWERPC64 !TARGET_64BIT + /* Copy and paste from linux64.h and freebsd64.h */ #undef TARGET_AIX #define TARGET_AIX TARGET_64BIT
prev parent reply other threads:[~2024-02-07 14:08 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-106680-4@http.gcc.gnu.org/bugzilla/> 2022-08-29 8:52 ` linkw at gcc dot gnu.org 2022-12-27 10:14 ` cvs-commit at gcc dot gnu.org 2023-01-04 5:21 ` linkw at gcc dot gnu.org 2024-01-20 11:27 ` sebastian.huber@embedded-brains.de 2024-01-20 11:33 ` sebastian.huber@embedded-brains.de 2024-02-05 12:54 ` linkw at gcc dot gnu.org 2024-02-05 13:01 ` sebastian.huber@embedded-brains.de 2024-02-05 13:03 ` linkw at gcc dot gnu.org 2024-02-05 13:08 ` sebastian.huber@embedded-brains.de 2024-02-05 13:24 ` linkw at gcc dot gnu.org 2024-02-05 13:30 ` linkw at gcc dot gnu.org 2024-02-05 13:38 ` sebastian.huber@embedded-brains.de 2024-02-07 14:08 ` sebastian.huber@embedded-brains.de [this message]
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-106680-4-HcIwAFPMFW@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).