From: Luca Bacci <luca.bacci982@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Checking for built-in functions from build systems
Date: Thu, 11 Aug 2022 00:16:23 +0200 [thread overview]
Message-ID: <CAJSEPt0kMz-Pet91T4GQmLjoC1ty5GbyHYecn-43fanEkx8YYg@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdQ-N0kGm6VaWCzb1b7ncN6gN6AJ0nMaMtFxdM0-SgzLWA@mail.gmail.com>
Thank you very much, Jonathan. That's very helpful!
This test program:
int main()
{
void *a = alloca(10);
return 0;
}
Compiles fine with:
gcc -o test test.c
But then fails with:
gcc -o test test.c -fno-builtin
That's on an Arch Linux system (based on glibc)
The issue is that what happens when built-ins are not inlined is not well
defined. The libc may not implement the routine, or it's not clear which
dependency should provide it.
Thanks,
Luca Bacci
Il giorno mer 10 ago 2022 alle ore 23:27 Jonathan Wakely <
jwakely.gcc@gmail.com> ha scritto:
>
>
> On Wed, 10 Aug 2022, 23:12 Luca Bacci via Gcc, <gcc@gcc.gnu.org> wrote:
>
>>
>> 1. Is inlining of built-ins dependant only on the target architecture and
>> command-line arguments?
>>
>
> No, I think it can depend on the arguments to the built-in as well.
>
>
> 2. If the answer to 1 is yes, could a __is_builtin_inlined (func) macro be
>> added to GCC? It should tell whether func is going to be substituted
>> inline
>> for the given compiler invocation
>
>
> I don't think that can work for some built-ins, e.g. in a single
> translation unit memcmp can be inlined for constant arguments of small
> size, and not inlined for other calls.
>
>
>
>
prev parent reply other threads:[~2022-08-10 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 21:11 Luca Bacci
2022-08-10 21:27 ` Jonathan Wakely
2022-08-10 22:16 ` Luca Bacci [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=CAJSEPt0kMz-Pet91T4GQmLjoC1ty5GbyHYecn-43fanEkx8YYg@mail.gmail.com \
--to=luca.bacci982@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).