From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: Ville Voutilainen <ville.voutilainen@gmail.com>,
Jonathan Wakely <jwakely@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Cc: gcc@gcc.gnu.org, libstdc++ <libstdc++@gcc.gnu.org>,
Libc-alpha <libc-alpha@sourceware.org>,
libc-coord@lists.openwall.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Expose 'array_length()' macro in <sys/param.h>
Date: Tue, 22 Sep 2020 11:10:08 +0200 [thread overview]
Message-ID: <34bae433-f67e-877d-f871-928cb55d2a87@gmail.com> (raw)
In-Reply-To: <CAFk2RUbEtvgFb_FZmcM9L4-g1kG_E7S2p9gveM0Z5Fe=zEDm9w@mail.gmail.com>
[[ CC += LKML ]]
Thanks for all your input. I learned some C++ :)
The following code works for all C and C++ standards:
g++ --std={c++98, c++03, c++11, c++14, c++17, c++20}
gcc --std={c89, c99, c11, c18, c2x}
With `-Wall -Wextra -Werror -pedantic -Wno-vla -Wno-sizeof-pointer-div`.
It doesn't compile when '+ __array_length(p)' is uncommented.
It compiles, and returns the correct value (18).
With some exceptions:
c++ doesn't accept the VLA (w[]):
array_length.c: In function 'int main()':
array_length.c:101:22: error: no matching function for call to
'__array_slength(int [y])'
101 | + __array_slength(w)
| ^
array_length.c:38:1: note: candidate: 'template<class T, long int N>
std::ptrdiff_t __array_slength(const T (&)[N])'
38 | __array_slength(const T(&)[N])
| ^~~~~~~~~~~~~~~
array_length.c:38:1: note: template argument deduction/substitution
failed:
array_length.c:101:22: note: variable-sized array type 'long int' is
not a valid template argument
101 | + __array_slength(w)
| ^
But we can live with limited support for VLAs in C++.
So I needed to comment '+ __array_slength(w)',
and then the program correctly returns 11.
As Ville suggested, I renamed the function/macro to __array_[s]length().
However, (some) BSDs already provide nitems() in <sys/param.h>,
so it probably wouldn't be very drastic to
provide this function/macro with the name '[s]nitems()' there.
Would you like to add anything else before I write the patch?
BTW, I should note one more thing:
Linux has a macro named '__must_be_array()' with the same API,
but slightly different internal implementation,
so they should be aware of this change.
However, I don't think they include <sys/param.h> a lot,
so maybe it doesn't break anything; but they should be aware anyway.
I CC'd the LKML so they are aware and can give any suggestions.
Thanks,
Alex
------------------------------------------------------------------------
#if defined(__cplusplus)
# include <cstddef>
# if __cplusplus >= 201703L
# include <iterator>
# endif
template<typename T, std::size_t N>
# if __cplusplus >= 201103L
constexpr
# endif
inline std::size_t
# if __cplusplus >= 201703L
__array_length(const T(&arr)[N])
# else
__array_length(const T(&)[N])
# endif
# if __cplusplus >= 201103L
noexcept
# endif
{
# if __cplusplus >= 201703L
return std::size(arr);
# else
return N;
# endif
}
template<typename T, std::ptrdiff_t N>
# if __cplusplus >= 201103L
constexpr
# endif
inline std::ptrdiff_t
# if __cplusplus >= 202002L
__array_slength(const T(&arr)[N])
# else
__array_slength(const T(&)[N])
# endif
# if __cplusplus >= 201103L
noexcept
# endif
{
# if __cplusplus >= 202002L
return std::ssize(arr);
# else
return N;
# endif
}
#else /* !defined(__cplusplus) */
#include <stddef.h>
# define __is_same_type(a, b) \
__builtin_types_compatible_p(__typeof__(a), __typeof__(b))
# define __is_array(arr) (!__is_same_type((arr), &(arr)[0]))
# if __STDC_VERSION__ >= 201112L
# define __must_be(e, msg) ( \
0 * (int)sizeof( \
struct { \
_Static_assert((e), msg); \
char ISO_C_forbids_a_struct_with_no_members__; \
} \
) \
)
# else
# define __must_be(e, msg) ( \
0 * (int)sizeof( \
struct { \
int : (-!(e)); \
char ISO_C_forbids_a_struct_with_no_members__; \
} \
) \
)
# endif
# define __must_be_array(arr) __must_be(__is_array(arr), "Must be an
array!")
# define __array_len(arr) (sizeof(arr) / sizeof((arr)[0]))
# define __array_length(arr) (__array_len(arr) + __must_be_array(arr))
# define __array_slength(arr) ((ptrdiff_t)__array_length(arr))
#endif
int main(void)
{
int a[5];
const int x = 6;
int v[x];
int y = 7;
int w[y];
int *p;
(void)p;
(void)v;
(void)w;
return __array_slength(a)
+ __array_slength(v)
+ __array_slength(w)
// + __array_length(p)
;
}
next prev parent reply other threads:[~2020-09-22 9:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 23:00 Expose 'array_length()' macro in <sys/cdefs.h> or <sys/param.h> Alejandro Colomar
2020-09-21 8:38 ` Florian Weimer
2020-09-21 10:11 ` Alejandro Colomar
2020-09-21 10:33 ` Florian Weimer
2020-09-21 12:47 ` Alejandro Colomar
2020-09-21 15:47 ` [libc-coord] " enh
2020-09-22 16:25 ` Rich Felker
2020-09-22 16:44 ` Jonathan Wakely
2020-09-22 16:53 ` Ville Voutilainen
2020-09-21 14:01 ` Jonathan Wakely
2020-09-21 21:52 ` Expose 'array_length()' macro in <sys/param.h> Alejandro Colomar
2020-09-21 22:04 ` Jonathan Wakely
2020-09-21 22:13 ` Ville Voutilainen
2020-09-22 9:10 ` Alejandro Colomar [this message]
2020-09-22 9:40 ` Jonathan Wakely
2020-09-22 10:01 ` Florian Weimer
2020-09-22 10:35 ` Alejandro Colomar
2020-09-22 11:40 ` Florian Weimer
2020-09-22 14:58 ` [RFC] <sys/param.h>: Add nitems() and snitems() macros Alejandro Colomar
2020-09-25 13:20 ` [PATCH v2] " Alejandro Colomar
2020-09-25 14:10 ` Alejandro Colomar
2020-09-25 14:48 ` Jonathan Wakely
2020-09-25 16:30 ` Alejandro Colomar
2020-09-25 17:39 ` Jonathan Wakely
2020-09-25 17:42 ` Jonathan Wakely
2020-09-25 17:46 ` Alejandro Colomar
2020-09-25 19:37 ` [PATCH v3] <sys/param.h>: Add nitems() Alejandro Colomar
2020-09-22 9:16 ` [libc-coord] Re: Expose 'array_length()' macro in <sys/param.h> Florian Weimer
2020-09-30 15:58 ` Expose 'array_length()' macro in <sys/cdefs.h> or <sys/param.h> Joseph Myers
2020-09-30 20:39 ` Alejandro Colomar
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=34bae433-f67e-877d-f871-928cb55d2a87@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-coord@lists.openwall.com \
--cc=libstdc++@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.voutilainen@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).