diff options
author | Jason Merrill <jason@redhat.com> | 2024-02-12 18:24:00 -0500 |
---|---|---|
committer | Jason Merrill <jason@redhat.com> | 2024-05-01 11:44:13 -0400 |
commit | c3bc2787b8beb7aae67fdf2a7f7271a9a4edca7c (patch) | |
tree | cf9589f3453380733238ab09459e55d19f0eeb33 /gcc/objc | |
parent | 0695aba3e987f4bb06c95f29ff90a8a3234e1507 (diff) | |
download | gcc-c3bc2787b8beb7aae67fdf2a7f7271a9a4edca7c.zip gcc-c3bc2787b8beb7aae67fdf2a7f7271a9a4edca7c.tar.gz gcc-c3bc2787b8beb7aae67fdf2a7f7271a9a4edca7c.tar.bz2 |
c++: const void* memchr [PR113706]
The C++ standard specifies that the <string.h> functions have const and
non-const overloads, unlike C's single function with const argument and
non-const return. Many systems don't actually implement this, but only add
an overload with non-const argument, so both end up having non-const return.
Solaris <string.h> does what the standard says, but we were penalizing it by
not recognizing the const overload as the built-in memchr.
PR c++/113706
gcc/cp/ChangeLog:
* decl.cc (decls_match): Handle memchr return type being
const-qualified.
gcc/testsuite/ChangeLog:
* g++.dg/opt/const-builtin1.C: New test.
* c-c++-common/pr103798-2.c: Remove xfail.
Diffstat (limited to 'gcc/objc')
0 files changed, 0 insertions, 0 deletions