public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113706] c-c++-common/pr103798-2.c FAILs as C++
Date: Wed, 01 May 2024 15:44:24 +0000	[thread overview]
Message-ID: <bug-113706-4-xpWIFmAovF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113706-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113706

--- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:c3bc2787b8beb7aae67fdf2a7f7271a9a4edca7c

commit r15-91-gc3bc2787b8beb7aae67fdf2a7f7271a9a4edca7c
Author: Jason Merrill <jason@redhat.com>
Date:   Mon Feb 12 18:24:00 2024 -0500

    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.

  parent reply	other threads:[~2024-05-01 15:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 15:52 [Bug tree-optimization/113706] New: " ro at gcc dot gnu.org
2024-02-01 15:54 ` [Bug tree-optimization/113706] " ro at gcc dot gnu.org
2024-02-01 15:55 ` ro at gcc dot gnu.org
2024-02-01 15:55 ` ro at gcc dot gnu.org
2024-02-01 16:58 ` hjl.tools at gmail dot com
2024-02-02  9:19 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-02-02 15:24 ` ro at gcc dot gnu.org
2024-02-13 10:30 ` ro at gcc dot gnu.org
2024-02-13 18:22 ` [Bug c++/113706] " jason at gcc dot gnu.org
2024-02-14  8:25 ` cvs-commit at gcc dot gnu.org
2024-02-14  8:28 ` ro at gcc dot gnu.org
2024-02-14 13:57 ` jason at gcc dot gnu.org
2024-02-14 13:59 ` jason at gcc dot gnu.org
2024-04-18 11:15 ` cvs-commit at gcc dot gnu.org
2024-05-01 15:44 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-01 15:47 ` jason at gcc dot gnu.org
2024-05-02 12:46 ` ro at CeBiTec dot Uni-Bielefeld.DE

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=bug-113706-4-xpWIFmAovF@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).