From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Using glibc headers with non-GCC compilers which define _Float32 etc.
Date: Mon, 03 Apr 2023 11:54:06 +0200 [thread overview]
Message-ID: <87ttxx47gh.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <mvmr0t1qqk8.fsf@suse.de> (Andreas Schwab's message of "Mon, 03 Apr 2023 11:10:31 +0200")
* Andreas Schwab:
> On Apr 03 2023, Florian Weimer wrote:
>
>> The -U__GNUC__ option is just a shortcut for reproduction. I think the
>> fundamental issue is that our headers do not work if the compiler does
>> not define __GNUC__, but predefines types like _Float32.
>
> That's a different case.
It's what I wanted to discuss, per the subject line.
> We should identify those specific compilers, and adjust the expression
> accordingly. But we can only support compilers that we can identify.
That's a reasonable position. I'll try to figure out which compiler
this is actually about.
Thanks,
Florian
prev parent reply other threads:[~2023-04-03 9:54 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
2023-04-03 9:03 ` Florian Weimer
2023-04-03 9:10 ` Andreas Schwab
2023-04-03 9:54 ` Florian Weimer [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=87ttxx47gh.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).