Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: dflogeras2 at gmail dot com
Target Milestone: ---
After upgrading to gcc-6.4.0, one of my regression tests fails to compile. I
boiled it down to the following simple code which fails to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82310
--- Comment #2 from Dave Flogeras ---
Sorry for the noise, it seems to be a glibc bug. Looks like it was fixed in
2.25 (too recent for my affected system). In case anyone else hits it and
finds this bug, see below:
https://sourceware.org/bugzi
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: dflogeras2 at gmail dot com
Target Milestone: ---
The ARM people recommend using -fsingle-precision-constant for targeting their
microcontrollers, such as the Cortex M4. I am
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67309
--- Comment #3 from Dave Flogeras ---
That is what is weird to me, it definitely used to compile for me with GCC
4.7.3 and 4.8.3 (with the same build system flags).
Is there anything that is conditional when compiling GCC that maybe the Gentoo
c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67309
--- Comment #5 from Dave Flogeras ---
Definitely, this project is my testbed for playing with new C++ features on a
STM32F4 micro. I also checked the ChibiOS (the RTOS I use) and it has always
had -fsingle-precision-constant defined (well for al
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67309
--- Comment #6 from Dave Flogeras ---
Created attachment 36237
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36237&action=edit
Patch for random.tcc
This patch made the test case presented compile cleanly for myself. It is from
GCC-4.8.4'
normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dflogeras2 at gmail dot com
GCC host triplet: Gentoo Linux
GCC target triplet: Target: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30019
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dflogeras2 at gmail dot com
Target Milestone: ---
Created attachment 53197
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53197&action=edit
Preprocessed src to reproduce bug
We hit this suspected bug co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106068
--- Comment #2 from Dave Flogeras ---
(In reply to Andrew Pinski from comment #1)
> You access an out of bounds for the array dhcp_rx_options_given in the while
> statement:
>
> while((dhcp_rx_options_given[8 + n] != 0) && (n < 2)) {
>
>
>
