From: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Development <gcc@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Subject: Re: [RFC] Adding a new attribute to function param to mark it as constant
Date: Wed, 4 Aug 2021 15:20:45 +0530 [thread overview]
Message-ID: <CAAgBjMnr+XVQyuo1zH4gEC_7qeQ7vMSGsA=Q5HEvy6_c9T5utg@mail.gmail.com> (raw)
In-Reply-To: <20210803215538.GU1583@gate.crashing.org>
On Wed, 4 Aug 2021 at 03:27, Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> Hi!
>
> On Fri, Jul 23, 2021 at 04:23:42PM +0530, Prathamesh Kulkarni via Gcc wrote:
> > The constraint here is that, vshl_n<type> intrinsics require that the
> > second arg (__b),
> > should be an immediate value.
>
> Something that matches the "n" constraint, not necessarily a literal,
> but stricter than just "immediate". It probably is a good idea to allow
> only "integer constant expression"s, so that the validity of the source
> code does not depend on what the optimisers do with the code.
>
> > As Richard suggested, sth like:
> > void foo(int x __attribute__((literal_constant (min_val, max_val)));
>
> The Linux kernel has a macro __is_constexpr to test if something is an
> integer constant expression, see <linux/const.h> . That is a much
> better idea imo. There could be a builtin for that of course, but an
> attribute is less powerful, less usable, less useful.
Hi Segher,
Thanks for the suggestions. I am not sure tho if we could use a macro
similar to __is_constexpr
to check if parameter is constant inside an inline function (which is
the case for intrinsics) ?
For eg:
#define __is_constexpr(x) \
(sizeof(int) == sizeof(*(8 ? ((void *)((long)(x) * 0l)) : (int *)8)))
inline int foo(const int x)
{
_Static_assert (__is_constexpr (x));
return x;
}
int main()
{
return foo (1);
}
results in:
foo.c: In function ‘foo’:
foo.c:8:3: error: static assertion failed
8 | _Static_assert (__is_constexpr (x));
Initially we tried to use __Static_assert (__builtin_constant_p (arg))
for the same purpose but that did not work
because while parsing the intrinsic function, the FE cannot determine
if the arg is indeed a constant.
I guess the static assertion or __is_constexpr would work only if the
intrinsic were defined as a macro instead of an inline function ?
Or am I misunderstanding ?
Thanks,
Prathamesh
>
>
> Segher
next prev parent reply other threads:[~2021-08-04 9:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 10:53 Prathamesh Kulkarni
2021-07-23 17:59 ` Andrew Pinski
2021-07-26 9:04 ` Prathamesh Kulkarni
2021-07-27 8:19 ` Richard Biener
2021-08-03 10:11 ` Prathamesh Kulkarni
2021-08-03 10:13 ` Prathamesh Kulkarni
2021-08-03 17:44 ` Martin Sebor
2021-08-04 9:46 ` Richard Earnshaw
2021-08-06 0:06 ` Martin Sebor
2021-08-06 10:51 ` Richard Earnshaw
2021-08-06 20:39 ` Martin Sebor
2021-08-12 8:32 ` Prathamesh Kulkarni
2021-08-13 17:14 ` Martin Sebor
2021-08-18 6:52 ` Prathamesh Kulkarni
2021-08-18 14:40 ` Martin Sebor
2021-08-19 8:10 ` Prathamesh Kulkarni
2021-08-03 21:55 ` Segher Boessenkool
2021-08-04 9:50 ` Prathamesh Kulkarni [this message]
2021-08-04 10:17 ` Segher Boessenkool
2021-08-04 11:50 ` Prathamesh Kulkarni
2021-08-04 12:46 ` Segher Boessenkool
2021-08-04 13:00 ` Richard Earnshaw
2021-08-04 13:40 ` Segher Boessenkool
2021-08-04 14:27 ` Richard Earnshaw
2021-08-04 16:16 ` Segher Boessenkool
2021-08-04 17:08 ` Florian Weimer
2021-08-04 17:59 ` Segher Boessenkool
2021-08-05 9:32 ` Richard Earnshaw
2021-08-05 9:01 ` Prathamesh Kulkarni
2021-08-05 15:06 ` Segher Boessenkool
2021-08-06 20:10 Martin Uecker
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='CAAgBjMnr+XVQyuo1zH4gEC_7qeQ7vMSGsA=Q5HEvy6_c9T5utg@mail.gmail.com' \
--to=prathamesh.kulkarni@linaro.org \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=gcc@gcc.gnu.org \
--cc=segher@kernel.crashing.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).