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 libstdc++/96083] Clang can't compile <ext/throw_allocator.h>: error: use of undeclared identifier '__builtin_sprintf'
Date: Mon, 11 Jan 2021 15:04:42 +0000	[thread overview]
Message-ID: <bug-96083-4-A1widte8mm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96083-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:93beee71a5ba5ee97a072d94780b140ae159fd74

commit r10-9250-g93beee71a5ba5ee97a072d94780b140ae159fd74
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Dec 16 13:50:34 2020 +0000

    libstdc++: Only use __builtin_sprintf if supported [PR 96083]

    Clang doesn't support __builtin_sprintf, so use std::sprintf instead.

    libstdc++-v3/ChangeLog:

            PR libstdc++/96083
            * include/ext/throw_allocator.h: Use __has_builtin to check for
            __builtin_sprintf support, and use std::sprintf if necessary.

    (cherry picked from commit 96d9670e88333d8896a5d2f2bb0403c1e2ad19ab)

  parent reply	other threads:[~2021-01-11 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 16:43 [Bug libstdc++/96083] New: " redi at gcc dot gnu.org
2020-12-16 14:33 ` [Bug libstdc++/96083] " cvs-commit at gcc dot gnu.org
2021-01-11 15:04 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-11 17:52 ` redi at gcc dot gnu.org

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-96083-4-A1widte8mm@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).