: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: g...@christoph-conrads.name
Target Milestone: ---
Created attachment 46090
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46090&action=edit
The initial state in combination with the incorrect carry comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89979
--- Comment #1 from Christoph Conrads ---
There is no attachment with the preprocessed code demonstrating the problem
because the this code is 1.2 MB large.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80977
Christoph Conrads changed:
What|Removed |Added
CC||g...@christoph-conrads.name
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80977
--- Comment #2 from Christoph Conrads ---
Created attachment 44802
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44802&action=edit
Patch proposal for GCC bug 80977
This patch attempts to fix bug 80977. The code in __generate_impl was not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80977
--- Comment #3 from Christoph Conrads ---
With GCC bug 80977, half of all values from the random bit generator may be
ignored by std::uniform_int_distribution.
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: g...@christoph-conrads.name
Target Milestone: ---
Consider the following C++11 code:
$ cat nan.cpp
#include
constexpr bool foo(double x)
{
return !(x <= 0);
}
int m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88173
--- Comment #1 from Christoph Conrads ---
Created attachment 45075
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45075&action=edit
Code pre-processed with GCC 7.3.0 on Ubuntu 18.04 LTS
This file was created with
$ g++ -Wextra -Wall -std=c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88173
--- Comment #2 from Christoph Conrads ---
Created attachment 45076
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45076&action=edit
Code pre-processed with GCC 6.3.0 on Raspbian 9.4
The file was created with
$ g++ -Wextra -Wall -std=c++11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88173
--- Comment #5 from Christoph Conrads ---
Having read the comments, I began to modify code in the bug report. Apparently,
the bug is only triggered if QNaN is on the wrong side of the comparison
operator:
christoph:~$ cat nan-lhs.cpp
#include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88173
--- Comment #6 from Christoph Conrads ---
Created attachment 45080
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45080&action=edit
nan-lhs.ii created by GCC 7.3.0 on Ubuntu 18.04 LTS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88173
--- Comment #7 from Christoph Conrads ---
Created attachment 45081
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45081&action=edit
nan-lhs.ii created by GCC 6.3.0 on Raspbian 9.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88173
--- Comment #8 from Christoph Conrads ---
Created attachment 45082
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45082&action=edit
nan-lhs.cpp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88173
--- Comment #9 from Christoph Conrads ---
nan-lhs.cpp with `float` instead of `double` triggers the same error messages
with `QNaNf` in place of `QNaN`.
13 matches
Mail list logo
