public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/96952] __builtin_thread_pointer support cannot be probed
Date: Tue, 29 Sep 2020 15:24:15 +0000 [thread overview]
Message-ID: <bug-96952-4-uy4sFWZVEe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96952-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> The whole point of __has_builtin is to let you avoid the configure-time
> checks on compilers that support __has_builtin. If __has_builtin doesn't
> actually work, it's pointless that it even exists and indeed everyone should
> just pretend it doesn't exist and keep using configure-time checks for
> everything.
That would certainly restore the portability that __has_builtin has broken.
next prev parent reply other threads:[~2020-09-29 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 11:25 [Bug preprocessor/96952] New: " sorear at fastmail dot com
2020-09-07 11:32 ` [Bug preprocessor/96952] " fw at gcc dot gnu.org
2020-09-07 12:10 ` jakub at gcc dot gnu.org
2020-09-07 16:09 ` bugdal at aerifal dot cx
2020-09-29 7:19 ` ebotcazou at gcc dot gnu.org
2020-09-29 14:43 ` bugdal at aerifal dot cx
2020-09-29 15:24 ` ebotcazou at gcc dot gnu.org [this message]
2020-09-29 16:21 ` redi at gcc dot gnu.org
2020-09-29 19:06 ` ebotcazou at gcc dot gnu.org
2020-09-29 19:36 ` redi at gcc dot gnu.org
2023-08-15 0:58 ` [Bug c/96952] " hpa at zytor dot com
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-96952-4-uy4sFWZVEe@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: 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).