public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-9862] libquadmath: Provide __BYTE_ORDER, __LITTLE_ENDIAN and __BIG_ENDIAN definitions Date: Tue, 9 Apr 2024 07:42:13 +0000 (GMT) [thread overview] Message-ID: <20240409074213.7069B3858CDA@sourceware.org> (raw) https://gcc.gnu.org/g:21c9fd9688d9de9562b3cb491e4ab50ce09e663a commit r14-9862-g21c9fd9688d9de9562b3cb491e4ab50ce09e663a Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 9 09:40:45 2024 +0200 libquadmath: Provide __BYTE_ORDER, __LITTLE_ENDIAN and __BIG_ENDIAN definitions My earlier libquadmath change apparently broke mingw32 build, while on Linux <bits/endian.h> is included and defines these, on Mingw apparently that isn't the case, while soft-fp wants a guarantee that sfp-machine.h defines these. 2024-04-09 Jakub Jelinek <jakub@redhat.com> * sfp-machine.h (__LITTLE_ENDIAN, __BIG_ENDIAN, __BYTE_ORDER): Define if __BYTE_ORDER isn't defined. Diff: --- libquadmath/sfp-machine.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/libquadmath/sfp-machine.h b/libquadmath/sfp-machine.h index e37d5b3c656..906a09e7139 100644 --- a/libquadmath/sfp-machine.h +++ b/libquadmath/sfp-machine.h @@ -18,6 +18,11 @@ #define _FP_NANSIGN_Q 1 #define _FP_KEEPNANFRACP 1 #define _FP_TININESS_AFTER_ROUNDING 0 +#ifndef __BYTE_ORDER +#define __LITTLE_ENDIAN __ORDER_LITTLE_ENDIAN__ +#define __BIG_ENDIAN __ORDER_BIG_ENDIAN__ +#define __BYTE_ORDER __BYTE_ORDER__ +#endif #define _FP_DECL_EX \ unsigned int fp_roundmode __attribute__ ((unused)) = FP_RND_NEAREST; #define FP_ROUNDMODE fp_roundmode
reply other threads:[~2024-04-09 7:42 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240409074213.7069B3858CDA@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs@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).