public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107037] New: 541.leela_r compiling fail since r13-2779
Date: Mon, 26 Sep 2022 08:18:38 +0000 [thread overview]
Message-ID: <bug-107037-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107037
Bug ID: 107037
Summary: 541.leela_r compiling fail since r13-2779
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: guojiufu at gcc dot gnu.org
Target Milestone: ---
When building 541.leela_r from spec2017, I encounter one error:
include/c++/13.0.0/bitset: In instantiation of 'void
std::_Base_bitset<_Nw>::_M_do_reset() [with long unsigned int _Nw = 7]':
include/c++/13.0.0/bitset:1145:19: required from 'std::bitset<_Nb>&
std::bitset<_Nb>::reset() [with long unsigned int _Nb = 441]'
Playout.cpp:20:18: required from here
include/c++/13.0.0/bitset:187:13: error: forming reference to reference type
'long unsigned int (&)[7]'
187 | for (_WordT& __w : _M_w)
| ^~~
The command is
g++ -std=c++03 -m64 -c -o Playout.o -DSPEC -DNDEBUG -I.
-DSPEC_AUTO_SUPPRESS_OPENMP -Ofast -DSPEC_LP64 Playout.cpp
This issue is also reproducible on -O3 or -O2.
It seems compiling fine before commit
r13-2779-9194c13909b72d23e58fee72864a2663b12f6b19.
next reply other threads:[~2022-09-26 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 8:18 guojiufu at gcc dot gnu.org [this message]
2022-09-26 9:29 ` [Bug libstdc++/107037] [13 Regression] " rguenth at gcc dot gnu.org
2022-09-26 10:06 ` redi at gcc dot gnu.org
2022-09-26 12:59 ` cvs-commit at gcc dot gnu.org
2022-09-26 13:00 ` 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-107037-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).