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++/97570] avr-gcc: error: 'void* memalign' redeclared as different kind of entity Date: Mon, 19 Apr 2021 09:19:09 +0000 [thread overview] Message-ID: <bug-97570-4-1phu8lnkzk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97570-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97570 --- Comment #4 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:67e95b6908b842e437089e867e5eed6dbbe264f2 commit r10-9715-g67e95b6908b842e437089e867e5eed6dbbe264f2 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Oct 26 12:02:50 2020 +0000 libstdc++: Fix declarations of memalign etc. for freestanding [PR 97570] libstdc++-v3/ChangeLog: PR libstdc++/97570 * libsupc++/new_opa.cc: Declare size_t in global namespace. Remove unused header. (cherry picked from commit 93e9a7bcd5434a24c945de33cd7fa01a25f68418)
next prev parent reply other threads:[~2021-04-19 9:19 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-25 16:24 [Bug libstdc++/97570] New: " matwey.kornilov at gmail dot com 2020-10-26 10:49 ` [Bug libstdc++/97570] " redi at gcc dot gnu.org 2020-10-26 12:36 ` cvs-commit at gcc dot gnu.org 2020-10-26 12:36 ` redi at gcc dot gnu.org 2020-10-26 12:38 ` redi at gcc dot gnu.org 2021-04-19 9:19 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-19 9:50 ` cvs-commit at gcc dot gnu.org 2021-04-19 10:00 ` cvs-commit at gcc dot gnu.org 2021-04-19 10:01 ` redi at gcc dot gnu.org 2021-04-19 10:40 ` redi at gcc dot gnu.org 2021-07-22 14:25 ` 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-97570-4-1phu8lnkzk@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: linkBe 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).