diff options
| author | Marek Polacek <polacek@redhat.com> | 2024-04-01 12:55:46 -0400 |
|---|---|---|
| committer | Marek Polacek <polacek@redhat.com> | 2024-04-02 14:32:29 -0400 |
| commit | 2f2924078ce51c2a0da3ad8f958f2d1de533969a (patch) | |
| tree | fec546799ef7887d73086b3eba1bd9cac80f7c78 /libgcc | |
| parent | daa2e7c7ffe49b788357f7f2c9ef1c9b125c1f8c (diff) | |
| download | gcc-2f2924078ce51c2a0da3ad8f958f2d1de533969a.zip gcc-2f2924078ce51c2a0da3ad8f958f2d1de533969a.tar.gz gcc-2f2924078ce51c2a0da3ad8f958f2d1de533969a.tar.bz2 | |
c++: make __is_array return false for T[0] [PR114479]
When we switched to using the __is_array built-in trait to implement
std::is_array in r14-6623-g7fd9c349e45534, we started saying that
T[0] is an array. There are various opinions as to whether that is
the best answer, but it seems prudent to keep the GCC 13 result.
PR c++/114479
gcc/cp/ChangeLog:
* semantics.cc (trait_expr_value) <case CPTK_IS_ARRAY>: Return false
for zero-sized arrays.
gcc/testsuite/ChangeLog:
* g++.dg/ext/is_array.C: Extend.
Diffstat (limited to 'libgcc')
0 files changed, 0 insertions, 0 deletions