[Bug tree-optimization/55616] New: bogus warning about undefined overflow after overflow check

2012-12-07 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55616 Bug #: 55616 Summary: bogus warning about undefined overflow after overflow check Classification: Unclassified Product: gcc Version: 4.8.0 Status:

[Bug tree-optimization/55616] bogus warning about undefined overflow after overflow check

2013-01-31 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55616 Florian Weimer fweimer at redhat dot com changed: What|Removed |Added CC||than

[Bug tree-optimization/55616] bogus warning about undefined overflow after overflow check

2013-01-31 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55616 --- Comment #4 from Florian Weimer fweimer at redhat dot com 2013-01-31 10:26:12 UTC --- (In reply to comment #3) I don't see anything bogus on the warning, it is useful to inform the developer about potentially unintended optimization

[Bug tree-optimization/55616] bogus warning about undefined overflow after overflow check

2013-01-31 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55616 --- Comment #7 from Florian Weimer fweimer at redhat dot com 2013-01-31 11:05:48 UTC --- (In reply to comment #6) Just write number_of_elements_in_path+100U or use unsigned type for number_of_elements_in_path Thanks

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-06 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 Florian Weimer fweimer at redhat dot com changed: What|Removed |Added CC||fweimer

[Bug rtl-optimization/54365] ARM optimization bug when pointer arithmetic wraps

2012-08-27 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54365 Florian Weimer fweimer at redhat dot com changed: What|Removed |Added CC||fweimer

[Bug rtl-optimization/54365] ARM optimization bug when pointer arithmetic wraps

2012-08-30 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54365 --- Comment #6 from Florian Weimer fweimer at redhat dot com 2012-08-30 13:33:05 UTC --- (In reply to comment #5) -fwrapv doesn't appear to make a difference: $ gcc compilerbug.c $ ./a.out it wraps $ gcc -O2 compilerbug.c $ ./a.out

[Bug rtl-optimization/54365] ARM optimization bug when pointer arithmetic wraps

2012-08-30 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54365 --- Comment #8 from Florian Weimer fweimer at redhat dot com 2012-08-30 13:56:04 UTC --- (In reply to comment #7) This is not surprising, just use integer arithmetic instead of pointer arithmetic. Pointer arithmetic not only has undefined

[Bug libstdc++/54388] [4.7/4.8 Regression] std::array.at() const results in undefined behaviour

2012-08-30 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54388 --- Comment #10 from Florian Weimer fweimer at redhat dot com 2012-08-30 15:39:21 UTC --- (In reply to comment #9) BTW, we definitely need a comment on why this particular code is so tricky. // NB: Interesting use of comma operator

[Bug c++/19351] [DR 624] operator new[] can return heap blocks which are too small

2012-07-17 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19351 Florian Weimer fweimer at redhat dot com changed: What|Removed |Added CC||fweimer

[Bug c/58270] Wrong code while accessing array elements in a global structure

2013-08-29 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58270 --- Comment #1 from Florian Weimer fweimer at redhat dot com --- The compiler is free to assume that both i1 and i2 are zero and the first store is dead (because this is the only valid array index). So if the buggy() function stores a value

[Bug middle-end/59711] New: ICE in force_constant_size, at gimplify.c:619 (nested function and variably-modified type)

2014-01-07 Thread fweimer at redhat dot com
Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: fweimer at redhat dot com Created attachment 31764 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=31764action=edit u.c The attached test case ICEs

[Bug middle-end/59711] ICE in force_constant_size, at gimplify.c:619 (nested function and variably-modified type)

2014-01-07 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59711 --- Comment #1 from Florian Weimer fweimer at redhat dot com --- Created attachment 31765 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=31765action=edit funcpointer.c Test case without nested function.

[Bug middle-end/59711] ICE in force_constant_size, at gimplify.c:619 with variably-modified return type

2014-01-08 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59711 --- Comment #6 from Florian Weimer fweimer at redhat dot com --- Created attachment 31772 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=31772action=edit pr59711.adb Here's the same thing in Ada (where it actually works—it's actually fairly

[Bug c/7652] -Wswitch-break : Warn if a switch case falls through

2014-04-30 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7652 --- Comment #25 from Florian Weimer fweimer at redhat dot com --- (In reply to Matthew Woehlke from comment #22) case B: ... [[gcc:fallthrough]] // suppress warning for fall-through to 'case C' Do we have such attributes in the C

[Bug c/7652] -Wswitch-break : Warn if a switch case falls through

2014-04-30 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7652 --- Comment #30 from Florian Weimer fweimer at redhat dot com --- (In reply to Manuel López-Ibáñez from comment #29) I like the previous suggestion of using goto LABEL;. In fact, the warning message could explicitly say use %goto %D;% to silence

[Bug fortran/61126] New: gfortran does not enable -Wununused-parameter with -Wextra

2014-05-09 Thread fweimer at redhat dot com
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: fweimer at redhat dot com The gfortran.dg/wextra_1.f test case assumes that -Wextra enables -Wununused-parameter, but this does not happen. No warning is printed on line 4, leading

[Bug fortran/61126] gfortran does not enable -Wununused-parameter with -Wextra

2014-05-09 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61126 --- Comment #3 from Florian Weimer fweimer at redhat dot com --- (In reply to Matthias Klose from comment #2) -Wunused-parameter is enabled by -Wall. I'm surprised that -Wextra is used without -Wall, but it happens in the testsuite in more

[Bug rtl-optimization/65220] New: Regression: integer division in stack alignment for VLA allocation

2015-02-26 Thread fweimer at redhat dot com
Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: fweimer at redhat dot com This sample program: int f(void *); void g(void) { unsigned size = 128; while (1) { unsigned buf[size]; if (f(buf

[Bug target/56726] i386: MALLOC_ABI_ALIGNMENT is too small (usually)

2015-04-02 Thread fweimer at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56726 Florian Weimer fweimer at redhat dot com changed: What|Removed |Added CC||fweimer

[Bug target/56726] i386: MALLOC_ABI_ALIGNMENT is too small (usually)

2015-04-06 Thread fweimer at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56726 --- Comment #12 from Florian Weimer fweimer at redhat dot com --- (In reply to Chip Salzenberg from comment #11) Indeed, 16 is required by the ABI; see http://www.x86-64.org/documentation/abi.pdf page 12. Only the SIMD __m256 is bigger than

[Bug ada/67205] New: Unnecessary trampolines for nested packages

2015-08-13 Thread fweimer at redhat dot com
Assignee: unassigned at gcc dot gnu.org Reporter: fweimer at redhat dot com CC: polacek at redhat dot com Target Milestone: --- Created attachment 36179 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36179action=edit trampoline.adb The attached example

[Bug ada/67205] violation of No_Implicit_Dynamic_Code restriction not reported

2015-09-10 Thread fweimer at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67205 --- Comment #3 from Florian Weimer --- (In reply to Eric Botcazou from comment #2) > > The attached example requires generation of trampolines. This may be due to > > bug 57999, but I think a front-end fix would be more reliable. > > Please

[Bug ada/67205] violation of No_Implicit_Dynamic_Code restriction not reported

2015-09-10 Thread fweimer at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67205 --- Comment #5 from Florian Weimer --- (In reply to Eric Botcazou from comment #4) > The truth is, the versions of GNAT released by AdaCore use a general scheme > to eliminate (almost) all trampolines, at least on native platforms, so > there is

[Bug libstdc++/65142] std::random_device Ignores Read Return Code

2015-09-14 Thread fweimer at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65142 Florian Weimer changed: What|Removed |Added CC||fweimer at redhat dot com --- Comment

[Bug libstdc++/65142] std::random_device Ignores Read Return Code

2015-09-14 Thread fweimer at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65142 --- Comment #5 from Florian Weimer --- The fix is incomplete because short reads can happen in practice for /dev/random at least. The usual retry loop is needed. It is not clear what to do on EINTR.

[Bug preprocessor/99315] New: #pragma GCC warning does not concatenate string literals

2021-03-01 Thread fweimer at redhat dot com via Gcc-bugs
Priority: P3 Component: preprocessor Assignee: unassigned at gcc dot gnu.org Reporter: fweimer at redhat dot com Target Milestone: --- This: #pragma GCC warning "foo" "bar" #pragma GCC error "foo" "bar" produces: /tmp/t.c:1:21:

[Bug c++/101747] New: Two-argument version of attribute malloc does not perform overload resolution

2021-08-03 Thread fweimer at redhat dot com via Gcc-bugs
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: fweimer at redhat dot com Target Milestone: --- This: struct T1; struct T2; void close(T1*); void close(T2*); T1* open(const char *) __attribute__ ((__malloc__ (close