: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: aaron at aarongraham dot com
Target Milestone: ---
https://godbolt.org/z/YGra91Woa
#include
int main() {
// This causes a format-overflow warning
: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: aaron at aarongraham dot com
Target Milestone: ---
gcc does not allow this to compile:
std::less<>{}(std::strong_ordering::less, 0);
Even though `std::strong_ordering::le
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: aaron at aarongraham dot com
Target Milestone: ---
Experiment here: https://godbolt.org/z/PT73cn5e5
#include
using clk = std::chrono::steady_clock;
bool
: unassigned at gcc dot gnu.org
Reporter: aaron at aarongraham dot com
Target Milestone: ---
Current implementation in has functions that violate
ODR:
std::experimental::net::ip::make_error_code
std::experimental::net::ip::make_error_condition
std::experimental::net::ip
++
Assignee: unassigned at gcc dot gnu.org
Reporter: aaron at aarongraham dot com
Target Milestone: ---
The following test, compiled via 'g++ -c test.cc':
#include
#include
using namespace std::chrono_literals;
extern void set_duration(std::chrono::nanoseconds);
int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58931
--- Comment #5 from Aaron Graham ---
Created attachment 43261
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43261=edit
Patch to check for overflow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=887
--- Comment #9 from Aaron Graham aaron at aarongraham dot com ---
Thanks. I had already patched our gcc so that gthreads cond always gets
initialized with CLOCK_MONOTONIC, then I switched __clock_t in
condition_variable to steady_clock
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58931
--- Comment #4 from Aaron Graham aaron at aarongraham dot com ---
See bug 41861 for discussion of steady_clock wrt condition_variable.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58931
Aaron Graham aaron at aarongraham dot com changed:
What|Removed |Added
CC||aaron
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63829
Aaron Graham aaron at aarongraham dot com changed:
What|Removed |Added
Component|c++ |libstdc
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: aaron at aarongraham dot com
ARM processor, Raspberry Pi
Offending code:
#include memory
thread_local std::unique_ptrint tls_test;
struct foo {
foo() { tls_test.reset(new int(42)); }
} const foo_instance
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63829
--- Comment #1 from Aaron Graham aaron at aarongraham dot com ---
Created attachment 33945
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33945action=edit
Disassembly of crashing result.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63829
--- Comment #2 from Aaron Graham aaron at aarongraham dot com ---
Created attachment 33946
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33946action=edit
Disassembly of good result.
--- Comment #6 from aaron at aarongraham dot com 2009-11-10 04:38 ---
So it appears that the problem is gthreads. The monotonic_clock support is
purely superficial in gcc until gthreads supports such a concept. Developers
will need to create their own clock and modify the standard
--- Comment #3 from aaron at aarongraham dot com 2009-10-29 15:53 ---
It appears that this one is fixed as of SVN revision 146566:
http://gcc.gnu.org/viewcvs/trunk/gcc/gthr-vxworks.h?view=log
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28808
15 matches
Mail list logo
