public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/102377] New: FAIL: 29_atomics/atomic_flag/cons/56012.cc with -std=gnu++20 Date: Thu, 16 Sep 2021 19:19:40 +0000 [thread overview] Message-ID: <bug-102377-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102377 Bug ID: 102377 Summary: FAIL: 29_atomics/atomic_flag/cons/56012.cc with -std=gnu++20 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org CC: rodgertq at gcc dot gnu.org Target Milestone: --- In file included from /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/atomic_base.h:41,^M from /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/atomic:41,^M from /home/jwakely/src/gcc/gcc/libstdc++-v3/testsuite/29_atomics/atomic_flag/cons/56012.cc:21:^M /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/atomic_wait.h:194: warning: use of 'std::hardware_destructive_interference_size' [-Winterference-size]^M /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/atomic_wait.h:194: note: its value can vary between compiler versions or with different '-mtune' or '-mcpu' flags^M /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/atomic_wait.h:194: note: if this use is part of a public ABI, change it to instead use a constant variable you define^M /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/atomic_wait.h:194: note: the default value for the current CPU tuning is 64 bytes^M /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/atomic_wait.h:194: note: you can stabilize this value with '--param hardware_destructive_interference_size=64', or disable this warning with '-Wno-interference-size'^M FAIL: 29_atomics/atomic_flag/cons/56012.cc (test for excess errors) Excess errors: /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/atomic_wait.h:194: warning: use of 'std::hardware_destructive_interference_size' [-Winterference-size] This is because <bits/atomic_wait.h> uses hardware_destructive_interference_size, which we probably don't want to do in the library headers.
next reply other threads:[~2021-09-16 19:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-16 19:19 redi at gcc dot gnu.org [this message] 2021-09-16 19:24 ` [Bug libstdc++/102377] " redi at gcc dot gnu.org 2021-09-16 22:33 ` rodgertq at gcc dot gnu.org 2021-09-25 20:06 ` redi at gcc dot gnu.org 2021-10-07 17:39 ` cvs-commit at gcc dot gnu.org 2021-10-07 17:40 ` 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-102377-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: 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).