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 target/100375] [12 Regression] trunk 20210501 ftbfs for nvptx-none Date: Tue, 04 May 2021 12:22:05 +0000 [thread overview] Message-ID: <bug-100375-4-Pdc9bFfXYV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100375-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100375 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:af08d7265bb5a82f3728737476c8098458a8d210 commit r9-9507-gaf08d7265bb5a82f3728737476c8098458a8d210 Author: Jakub Jelinek <jakub@redhat.com> Date: Sun May 2 14:17:23 2021 +0200 nvptx: Fix up nvptx build against latest libstdc++ [PR100375] The r12-220-gd96db15967e78d7cecea3b1cf3169ceb924678ac change deprecated some non-standard std::pair constructors and that apparently broke nvptx.c build, where pseudo_node_t is std::pair<struct basic_block_def *, int> and so nullptr (or NULL) needs to be used for the first argument of the ctors instead of 0. 2021-05-02 Jakub Jelinek <jakub@redhat.com> PR target/100375 * config/nvptx/nvptx.c (nvptx_sese_pseudo): Use NULL instead of 0 as first argument of pseudo_node_t constructors. (cherry picked from commit 7911a905276781c20f704f5a91b5125e0184d072)
next prev parent reply other threads:[~2021-05-04 12:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-01 15:26 [Bug target/100375] New: " doko at debian dot org 2021-05-01 16:00 ` [Bug target/100375] " jakub at gcc dot gnu.org 2021-05-01 16:08 ` redi at gcc dot gnu.org 2021-05-01 16:48 ` jakub at gcc dot gnu.org 2021-05-01 22:43 ` redi at gcc dot gnu.org 2021-05-02 12:18 ` cvs-commit at gcc dot gnu.org 2021-05-03 8:01 ` rguenth at gcc dot gnu.org 2021-05-03 14:22 ` redi at gcc dot gnu.org 2021-05-04 11:57 ` cvs-commit at gcc dot gnu.org 2021-05-04 12:08 ` cvs-commit at gcc dot gnu.org 2021-05-04 12:22 ` cvs-commit at gcc dot gnu.org [this message] 2021-05-04 12:26 ` cvs-commit 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-100375-4-Pdc9bFfXYV@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).