From: Alejandro Colomar <alx.manpages@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: linux-man@vger.kernel.org, JeanHeyd Meneide <wg14@soasis.org>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>,
Ingo Schwarze <schwarze@usta.de>
Subject: Re: [PATCH v2] _Generic.3: New page documenting _Generic()
Date: Fri, 9 Sep 2022 14:31:09 +0200 [thread overview]
Message-ID: <2fa3fc92-ac6d-0b49-3cc8-a668e5ac9246@gmail.com> (raw)
In-Reply-To: <28eb6a53-7865-d75d-8903-77b63e09222d@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3808 bytes --]
On 9/4/22 23:16, Alejandro Colomar wrote:
> Hi Florian,
>
> On 8/23/22 09:58, Florian Weimer wrote:
>> Note that this approach does not really work that well in practice
>> because macros using _Generic expand all the alternatives (in current
>> implementations; doing this differently requires deviating from the
>> layered implementation strategy suggested in the C standard). This
>> means that _Generic-using macros can only be nested maybe three or four
>> levels deep, depending on the number of _Generic alternatives on each
>> level. For <tgmath.h>, this is really not enough, so a high-quality
>> implementation of <tgmath.h> using _Generic is not feasible. GCC
>> provides __builtin_tgmath, which is designed in such a way that when
>> used in a macro, the macro argument is only expanded once.
>>
>> Maybe mention this under BUGS?
>>
>> C++ templates do not suffer from this particular problem.
>
>
> Heh, I don't know how this didn't oocur to me before. Well, maybe it's
> because it's non-standard (but the standard might very well benefit from
> adding this, IMO).
>
> An always_inline function with no extern definition behaves as if it
> were a macro (trying to take a pointer to it, or something that needs a
> linker symbol, will result in linker errors, which is not the most
> readable error, but good enough), in the sense that it doesn't have ABI
> issues, but has the benefit of not creating code exponentially.
>
>
> Cheers,
>
> Alex
>
> ---
>
> diff --git a/man3/_Generic.3 b/man3/_Generic.3
> index f3daf98c1..3bd5f306c 100644
> --- a/man3/_Generic.3
> +++ b/man3/_Generic.3
> @@ -30,7 +30,9 @@ C11 and later.
> The following program demonstrates how to write
> a replacement for the standard
> .BR imaxabs (3)
> -function, which being a function can't really provide what it promises:
> +function, which being an
> +.I extern
> +function can't really provide what it promises:
> seamlessly upgrading to the widest available type.
> .PP
> .\" SRC BEGIN (_Generic.c)
> @@ -39,11 +41,16 @@ seamlessly upgrading to the widest available type.
> #include <stdio.h>
> #include <stdlib.h>
>
> -#define my_imaxabs(j) _Generic(INTMAX_C(0), \e
> - long: labs(j), \e
> - long long: llabs(j) \e
> - /* long long long: lllabs(j) */ \e
> -)
> +[[gnu::always_inline]]
> +inline intmax_t
> +my_imaxabs(intmax_t j)
> +{
> + return _Generic(j,
> + long: labs(j),
> + long long: llabs(j)
> + /* long long long: lllabs(j) */
> + )
> +}
>
> int
> main(void)
>
Huh, although this goes back again to macros, and potentially
exponential code, I think it's quite clean and minimal, and has the
benefit that it allows one to take pointers:
$ cat gen.c
#include <stdint.h>
#include <stdio.h>
#include <stdlib.h>
#define my_imaxabs _Generic(INTMAX_C(0), \
long: labs, \
long long: llabs \
/* long long long: lllabs */ \
)
int
main(void)
{
off_t a;
a = -42;
printf("imaxabs(%jd) == %jd\n", (intmax_t) a, my_imaxabs(a));
printf("&imaxabs == %p\n", &my_imaxabs);
printf("&labs == %p\n", &labs);
printf("&llabs == %p\n", &llabs);
exit(EXIT_SUCCESS);
}
$ cc -Wall -Wextra gen.c
$ ./a.out
imaxabs(-42) == 42
&imaxabs == 0x7ff5aa2407a0
&labs == 0x7ff5aa2407a0
&llabs == 0x7ff5aa2407b0
Nice experiment :)
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-09-09 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 17:10 [PATCH] _Generic.3: New page documenting _Generic() Alejandro Colomar
2022-08-21 11:55 ` [PATCH v2] " Alejandro Colomar
2022-08-23 7:58 ` Florian Weimer
2022-08-23 13:16 ` Alejandro Colomar
2022-08-23 13:24 ` Alejandro Colomar
2022-08-23 13:32 ` Alejandro Colomar
2022-08-23 13:34 ` Alejandro Colomar
2022-09-04 21:16 ` Alejandro Colomar
2022-09-04 22:06 ` Alejandro Colomar
2022-09-09 12:31 ` Alejandro Colomar [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=2fa3fc92-ac6d-0b49-3cc8-a668e5ac9246@gmail.com \
--to=alx.manpages@gmail.com \
--cc=fweimer@redhat.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=schwarze@usta.de \
--cc=wg14@soasis.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