diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2025-02-07 14:27:18 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@gcc.gnu.org> | 2025-02-07 14:27:18 +0100 |
| commit | 6c8e6d6febaed3c167ca9534935c2cb18045528e (patch) | |
| tree | 4708e88786f38f6179c6e332bee08054d9c06405 /gcc/c/c-parser.cc | |
| parent | 251aa524a314faa749b7dd1b7da048e6e6476015 (diff) | |
| download | gcc-6c8e6d6febaed3c167ca9534935c2cb18045528e.zip gcc-6c8e6d6febaed3c167ca9534935c2cb18045528e.tar.gz gcc-6c8e6d6febaed3c167ca9534935c2cb18045528e.tar.bz2 | |
c++: Allow constexpr reads from volatile std::nullptr_t objects [PR118661]
As mentioned in the PR, https://eel.is/c++draft/conv.lval#note-1
says that even volatile reads from std::nullptr_t typed objects actually
don't read anything and https://eel.is/c++draft/expr.const#10.9
says that even those are ok in constant expressions.
So, the following patch adjusts the r9-4793 changes to have an exception
for NULLPTR_TYPE.
As [conv.lval]/3 also talks about accessing to inactive member, I've added
testcase to cover that as well.
2025-02-07 Jakub Jelinek <jakub@redhat.com>
PR c++/118661
* constexpr.cc (potential_constant_expression_1): Don't diagnose
lvalue-to-rvalue conversion of volatile lvalue if it has NULLPTR_TYPE.
* decl2.cc (decl_maybe_constant_var_p): Return true for constexpr
decls with NULLPTR_TYPE even if they are volatile.
* g++.dg/cpp0x/constexpr-volatile4.C: New test.
* g++.dg/cpp0x/constexpr-union9.C: New test.
Diffstat (limited to 'gcc/c/c-parser.cc')
0 files changed, 0 insertions, 0 deletions