public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100375] New: [12 Regression] trunk 20210501 ftbfs for nvptx-none
Date: Sat, 01 May 2021 15:26:22 +0000 [thread overview]
Message-ID: <bug-100375-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100375
Bug ID: 100375
Summary: [12 Regression] trunk 20210501 ftbfs for nvptx-none
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at debian dot org
Target Milestone: ---
trunk 20210501 ftbfs for nvptx-none, trying to build the offload compiler with
the just built trunk 20210501 x86_64-linux-gnu host build.
../../src-nvptx/gcc/config/nvptx/nvptx.c: In function 'void
nvptx_sese_pseudo(basic_block, bb_sese*, int, int, vec<e
dge_def*, va_gc>*, size_t)':
../../src-nvptx/gcc/config/nvptx/nvptx.c:3754:42: error: call of overloaded
'pair(int, int)' is ambiguous
3754 | node_back = pseudo_node_t (0, 0);
| ^
In file included from
/packages/gcc/snap/gcc-snapshot-20210501/build/x86_64-linux-gnu/libstdc++-v3/include/bits/stl_algobase.h:64,
from
/packages/gcc/snap/gcc-snapshot-20210501/build/x86_64-linux-gnu/libstdc++-v3/include/bits/char_traits.h:39,
from
/packages/gcc/snap/gcc-snapshot-20210501/build/x86_64-linux-gnu/libstdc++-v3/include/ios:40,
from
/packages/gcc/snap/gcc-snapshot-20210501/build/x86_64-linux-gnu/libstdc++-v3/include/istream:38,
from
/packages/gcc/snap/gcc-snapshot-20210501/build/x86_64-linux-gnu/libstdc++-v3/include/sstream:38,
next reply other threads:[~2021-05-01 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 15:26 doko at debian dot org [this message]
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
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@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).