https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017
--- Comment #38 from Andrew Aladjev ---
Sure, patches works perfect. But we need somehow decrease the chance of similar
regressions in future. It is possible by adding any basic "canadian" build into
the list of tests to be done before release.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017
--- Comment #35 from Andrew Aladjev ---
Hello cqwrteur, do you have an influence on core gcc developers? Please provide
an idea to add at least one "canadian" test before release. x86_64-pc-linux-gnu
-> x86_64-unknown-linux-gnu will be enough. W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017
--- Comment #32 from Andrew Aladjev ---
I've added include_next_fenv dirty patch. I want just to quickly explain how to
use it.
First of all I've noticed (many years ago) that gcc developers are making
releases based on limited set of basic tes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017
--- Comment #30 from Andrew Aladjev ---
Created attachment 51746
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51746&action=edit
Include fenv dirty patch for gcc 11.2.0
Please apply carefully, it is not safe.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99741
--- Comment #1 from Andrew Aladjev ---
PS https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89088 is another issue that may
be related to this one.
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: aladjev.andrew at gmail dot com
Target Milestone: ---
Created attachment 50466
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50466&action=edit
fit.tar.gz
Hello, please review the following cmake iss
ty: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: aladjev.andrew at gmail dot com
Created attachment 32900
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=32900&action=edit
test.c
Please checkout attached tes
