From: Andreas Schwab <schwab@suse.de>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>
Subject: Re: Using glibc headers with non-GCC compilers which define _Float32 etc.
Date: Mon, 03 Apr 2023 10:43:05 +0200 [thread overview]
Message-ID: <mvmv8idqrty.fsf@suse.de> (raw)
In-Reply-To: <87o7o575jl.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Mon, 03 Apr 2023 10:07:10 +0200")
On Apr 03 2023, Florian Weimer via Libc-alpha wrote:
> We have a downstream bug that points out that if __GNUC__ is not
> defined, glibc assumes that it's necessary to define _Float32 as a
> typedef to float:
>
> glibc: _FloatN and _FloatNx problem if _GNUC__ is not defined
> <https://bugzilla.redhat.com/show_bug.cgi?id=2183212>
>
> That does not work if the compiler already defines _Float32.
>
> What should we do about this?
I don't think we should support that use case. It's probably not the
only thing that will break in this situation.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-04-03 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 8:07 Florian Weimer
2023-04-03 8:43 ` Andreas Schwab [this message]
2023-04-03 9:03 ` Florian Weimer
2023-04-03 9:10 ` Andreas Schwab
2023-04-03 9:54 ` Florian Weimer
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=mvmv8idqrty.fsf@suse.de \
--to=schwab@suse.de \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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: link
Be 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).