public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/114103] FAIL: 29_atomics/atomic/lock_free_aliases.cc -std=gnu++20 (test for excess errors)
Date: Wed, 28 Feb 2024 01:04:26 +0000 [thread overview]
Message-ID: <bug-114103-4-CxoT9WdwmC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114103-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114103
--- Comment #9 from dave.anglin at bell dot net ---
On 2024-02-27 9:32 a.m., redi at gcc dot gnu.org wrote:
> Patch posted:
> https://gcc.gnu.org/pipermail/gcc-patches/2024-February/646619.html
Caused build error:
libtool: compile: /home/dave/gnu/gcc/objdir64/./gcc/xgcc -shared-libgcc
-B/home
/dave/gnu/gcc/objdir64/./gcc -nostdinc++
-L/home/dave/gnu/gcc/objdir64/hppa64-hp
-hpux11.11/libstdc++-v3/src
-L/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/li
bstdc++-v3/src/.libs
-L/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++
-v3/libsupc++/.libs -B/opt/gnu64/gcc/gcc-14/hppa64-hp-hpux11.11/bin/
-B/opt/gnu6
4/gcc/gcc-14/hppa64-hp-hpux11.11/lib/ -isystem
/opt/gnu64/gcc/gcc-14/hppa64-hp-h
pux11.11/include -isystem /opt/gnu64/gcc/gcc-14/hppa64-hp-hpux11.11/sys-include
-fno-checking -I/home/dave/gnu/gcc/gcc/libstdc++-v3/../libgcc
-I/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/hppa64-hp-hpux11.11
-I/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/libsupc++ -std=gnu++20
-D_GLIBCXX_SHARED -fno-implicit-templates -Wall -Wextra -Wwrite-strings
-Wcast-qual -Wabi=2 -fdiagnostics-show-location=once -ffunction-sections
-fdata-sections -frandom-seed=tzdb.lo -fimplicit-templates -O2 -g -I. -c
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc -DPIC
-D_GLIBCXX_SHARED -o tzdb.o
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:654:9: error:
'atomic_signed_lock_free' does not name a type
654 | atomic_signed_lock_free counter{0};
| ^~~~~~~~~~~~~~~~~~~~~~~
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:706:18: error:
'atomic_signed_lock_free' was not declared in this scope; did you mean
'atomic_is_lock_free'?
706 | RulesCounter<atomic_signed_lock_free> rules_counter;
| ^~~~~~~~~~~~~~~~~~~~~~~
| atomic_is_lock_free
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:706:41: error: template
argument 1 is invalid
706 | RulesCounter<atomic_signed_lock_free> rules_counter;
| ^
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc: In member function 'void
std::chrono::time_zone::_Impl::RulesCounter<_Tp>::increment()':
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:658:11: error: 'counter' was
not declared in this scope; did you mean 'count'?
658 | { counter.fetch_add(1, memory_order::relaxed); }
| ^~~~~~~
| count
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc: In member function 'void
std::chrono::time_zone::_Impl::RulesCounter<_Tp>::decrement()':
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:668:17: error: 'counter' was
not declared in this scope; did you mean 'count'?
668 | if (++counter == 0)
| ^~~~~~~
| count
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc: In member function 'void
std::chrono::time_zone::_Impl::RulesCounter<_Tp>::lock()':
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:679:25: error: 'counter' was
not declared in this scope; did you mean 'count'?
679 | for (auto c = counter.load(memory_order::relaxed); c != 0;)
| ^~~~~~~
| count
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc: In member function 'void
std::chrono::time_zone::_Impl::RulesCounter<_Tp>::unlock()':
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:697:24: error: 'counter' was
not declared in this scope; did you mean 'count'?
697 | if (auto c = counter.load(memory_order::relaxed); c < 0)
| ^~~~~~~
| count
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc: In member function
'std::chrono::sys_info
std::chrono::time_zone::_M_get_sys_info(std::chrono::sys_seconds) const':
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:969:32: error: request for
member 'decrement' in '((const
std::chrono::time_zone*)this)->std::chrono::time_zone::_M_impl.std::unique_ptr<std::chrono::time_zone::_Impl>::operator->()->std::chrono::time_zone::_Impl::rules_counter',
which is of non-class type 'int'
969 | _M_impl->rules_counter.decrement();
| ^~~~~~~~~
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc: In function 'const
std::chrono::tzdb& std::chrono::reload_tzdb()':
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:1488:38: error: request for
member 'increment' in
'impl.std::chrono::time_zone::_Impl::rules_counter', which is of non-class type
'int'
1488 | impl.rules_counter.increment();
| ^~~~~~~~~
In file included from
/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/bits/atomic_wait.h:51,
from
/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/bits/atomic_base.h:42,
from
/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/atomic:50,
from ../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:35:
/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/bits/std_mutex.h:
In instantiation of
'std::lock_guard<_Mutex>::lock_guard(mutex_type&) [with _Mutex = int;
mutex_type = int]':
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:779:43: required from here
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:1488:38: error: 779 |
lock_guard lock(_M_impl->rules_counter);
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:1488:38: error: |
^
/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/bits/std_mutex.h:250:19:
error: request for member 'lock' in
'((std::lock_guard<int>*)this)->std::lock_guard<int>::_M_device', which is of
non-class type 'std::lock_guard<int>::mutex_type' {aka 'int'}
250 | { _M_device.lock(); }
| ~~~~~~~~~~^~~~
/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/bits/std_mutex.h:
In instantiation of
'std::lock_guard<_Mutex>::~lock_guard() [with _Mutex = int]':
../../../../../gcc/libstdc++-v3/src/c++20/tzdb.cc:779:43: required from here
/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/bits/std_mutex.h:250:19:
error: 779 | lock_guard
lock(_M_impl->rules_counter);
/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/bits/std_mutex.h:250:19:
error:
| ^
/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/bits/std_mutex.h:257:19:
error: request for member 'unlock' in
'((std::lock_guard<int>*)this)->std::lock_guard<int>::_M_device', which is of
non-class type 'std::lock_guard<int>::mutex_type' {aka 'int'}
257 | { _M_device.unlock(); }
| ~~~~~~~~~~^~~~~~
make[6]: *** [Makefile:754: tzdb.lo] Error 1
next prev parent reply other threads:[~2024-02-28 1:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 17:47 [Bug libstdc++/114103] New: " danglin at gcc dot gnu.org
2024-02-26 10:54 ` [Bug libstdc++/114103] " redi at gcc dot gnu.org
2024-02-26 10:55 ` redi at gcc dot gnu.org
2024-02-26 10:56 ` redi at gcc dot gnu.org
2024-02-26 12:21 ` dave.anglin at bell dot net
2024-02-26 12:22 ` redi at gcc dot gnu.org
2024-02-26 12:25 ` dave.anglin at bell dot net
2024-02-27 14:32 ` redi at gcc dot gnu.org
2024-02-27 20:49 ` dave.anglin at bell dot net
2024-02-28 1:04 ` dave.anglin at bell dot net [this message]
2024-02-28 9:31 ` redi at gcc dot gnu.org
2024-02-29 17:44 ` redi at gcc dot gnu.org
2024-03-01 22:15 ` dave.anglin at bell dot net
2024-03-01 22:35 ` redi at gcc dot gnu.org
2024-03-01 22:38 ` redi at gcc dot gnu.org
2024-03-01 22:42 ` redi at gcc dot gnu.org
2024-03-02 23:36 ` dave.anglin at bell dot net
2024-03-07 21:00 ` cvs-commit at gcc dot gnu.org
2024-03-07 21:01 ` redi at gcc dot gnu.org
2024-03-23 18:12 ` danglin 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-114103-4-CxoT9WdwmC@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).