public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100298] New: noexcept is missing for thread::hardware_concurrency clang refuses the code
Date: Wed, 28 Apr 2021 00:18:11 +0000 [thread overview]
Message-ID: <bug-100298-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100298
Bug ID: 100298
Summary: noexcept is missing for thread::hardware_concurrency
clang refuses the code
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: unlvsur at live dot com
Target Milestone: ---
In file included from In file included from
/home/cqwrteur/myhome/libstdcxx_wasm_build/include/bits/atomic_futex.h:39:
In file included from
/home/cqwrteur/myhome/libstdcxx_wasm_build/include/mutex:47:
In file included from
/home/cqwrteur/myhome/libstdcxx_wasm_build/include/thread:43:
/home/cqwrteur/myhome/libstdcxx_wasm_build/include/bits/std_thread.h:273:31:
error: 'hardware_concurrency' is missing exception specification 'noexcept'
inline unsigned int thread::hardware_concurrency() { return 0; }
^
/home/cqwrteur/myhome/libstdcxx_wasm_build/include/bits/std_thread.h:196:5:
note: previous declaration is here
hardware_concurrency() noexcept;
^
1 warning and 1 error generated.
1 warning generated.
2 warnings generated.
1 warning and 1 error generated.
4 warnings generated.
make[3]: *** [Makefile:648: future.lo] Error 1
5 warnings generated.
make[3]: *** [Makefile:648: futex.lo] Error 1
next reply other threads:[~2021-04-28 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 0:18 unlvsur at live dot com [this message]
2021-04-28 11:45 ` [Bug libstdc++/100298] [11/12 Regression] " redi at gcc dot gnu.org
2021-04-28 11:55 ` cvs-commit at gcc dot gnu.org
2021-04-28 11:56 ` cvs-commit at gcc dot gnu.org
2021-04-28 11:57 ` 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-100298-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).