[Bug c/86768] New: gcc wrongly decides that variable is <=1 after "while (x>1 && blah)" construct.

2018-07-31 Thread Emmanuel.Thome at inria dot fr
IRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: Emmanuel.Thome at inria dot fr Target Milestone: --- Created attachment 44477 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44477=edit tes

[Bug c++/86733] c++17 and #pragma GCC diagnostic warning "-Wall" resurrect pre-c++11 warnings.

2018-07-31 Thread Emmanuel.Thome at inria dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86733 --- Comment #4 from Emmanuel Thomé --- (In reply to Jonathan Wakely from comment #3) > (In reply to Emmanuel Thomé from comment #2) > > (In reply to Jonathan Wakely from comment #1) > > > Presumably the handling for the pragma just turns the

[Bug c++/86733] c++17 and #pragma GCC diagnostic warning "-Wall" resurrect pre-c++11 warnings.

2018-07-31 Thread Emmanuel.Thome at inria dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86733 --- Comment #2 from Emmanuel Thomé --- (In reply to Jonathan Wakely from comment #1) > Presumably the handling for the pragma just turns the option on without > considering the current cxx_dialect. It seems to me that it is not consistent with

[Bug c++/86733] New: c++17 and #pragma GCC diagnostic warning "-Wall" resurrect pre-c++11 warnings.

2018-07-30 Thread Emmanuel.Thome at inria dot fr
NCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: Emmanuel.Thome at inria dot fr Target Milestone: --- gcc 8.1.0 here. The following simple code expectedly fails to compile with -std=c++98 because of the do

[Bug middle-end/67418] resolution to constant fails between pointer on stack and pointer within argument structure

2015-09-01 Thread Emmanuel.Thome at inria dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67418 --- Comment #2 from Emmanuel Thomé --- ok thanks. Indeed it's more an enhancement request then.

[Bug c/67418] New: resolution to constant fails between pointer on stack and pointer within argument structure

2015-09-01 Thread Emmanuel.Thome at inria dot fr
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: Emmanuel.Thome at inria dot fr Target Milestone: --- Hi, In the code below, gcc version 4.8.4, 4.9.3, and 5.2.0 fail to resolve the expression temp != a-&g

[Bug c/62294] [4.9 Regression] Missing passing argument [...] from incompatible pointer type warning.

2014-09-03 Thread Emmanuel.Thome at inria dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62294 --- Comment #6 from Emmanuel Thomé Emmanuel.Thome at inria dot fr --- Thanks. E.

[Bug c/62294] New: Missing passing argument [...] from incompatible pointer type warning.

2014-08-28 Thread Emmanuel.Thome at inria dot fr
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: Emmanuel.Thome at inria dot fr Hi. The following code should cause a warning. #include gmp.h void what(mpz_t a, mpz_t p, gmp_randstate_t rstate) { mpz_urandomm(a, p, rstate

[Bug tree-optimization/53198] [4.7 Regression] gcc wrongly emits array subscript is above array bounds for simple arrays

2013-10-14 Thread Emmanuel.Thome at inria dot fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53198 Emmanuel Thomé Emmanuel.Thome at inria dot fr changed: What|Removed |Added CC