From: Andrea Monaco <andrea.monaco@autistici.org>
To: schwab@linux-m68k.org, jwakely.gcc@gmail.com
Cc: gcc@gcc.gnu.org
Subject: Re: No type checking in ctype builtins
Date: Wed, 27 Apr 2022 20:07:00 +0200 [thread overview]
Message-ID: <87pml21juj.fsf@autistici.org> (raw)
In-Reply-To: <87mtg65xom.fsf@igel.home>
> Try -Wsystem-headers.
You're right. That showed a warning.
> You need to suppress the macro to get the builtin.
That means a macro expansion takes precedence over a builtin function
substitution, if I understand correctly. It makes sense, because
preprocessing happens before compilation.
Maybe we could mention that in the manual, for example in "6.59 Other
Built-in Functions Provided by GCC"
(https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html).
Andrea Monaco
next prev parent reply other threads:[~2022-04-27 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 15:29 Andrea Monaco
2022-04-27 15:54 ` Andreas Schwab
2022-04-27 18:07 ` Andrea Monaco [this message]
2022-04-28 11:13 ` Florian Weimer
2022-04-27 16:19 ` Jonathan Wakely
2022-04-28 12:02 ` Eric Gallager
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=87pml21juj.fsf@autistici.org \
--to=andrea.monaco@autistici.org \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=schwab@linux-m68k.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).