[Bug c++/55227] designated initializer for char array by string constant

2020-06-16 Thread steven.spark at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55227 Szikra changed: What|Removed |Added CC||steven.spark at gmail dot com --- Comment #5

[Bug c++/70774] New: constexpr function with reference parameter gives reinterpret_cast from integer to pointer error

2016-04-23 Thread steven.spark at gmail dot com
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: steven.spark at gmail dot com Target Milestone: --- Here is the simplified code: -- #define PORTX (*(volatile unsigned char *)(0x1B

[Bug c++/58798] class with a class reference member generates unjustified warning

2017-01-29 Thread steven.spark at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58798 Szikra changed: What|Removed |Added CC||steven.spark at gmail dot com --- Comment #1

[Bug c++/58798] class with a class reference member generates unjustified warning

2017-01-29 Thread steven.spark at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58798 --- Comment #2 from Szikra --- Created attachment 40615 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40615&action=edit preprocessed test case Compiled with g++ --save-temps -std=gnu++11 -fpack-struct eeprom.cpp -o eeprom eeprom.cpp: I

[Bug c++/58798] class with a class reference member generates unjustified warning

2017-01-29 Thread steven.spark at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58798 --- Comment #3 from Szikra --- The warning is still there if I use the -Wno-packed option: g++ -std=gnu++11 -fpack-struct -Wno-packed eeprom.cpp -o eeprom Why? I have found a suggestion to hide warning about ignored attributes: #pragma clang di

[Bug c++/58798] class with a class reference member generates unjustified warning

2017-01-30 Thread steven.spark at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58798 --- Comment #5 from Szikra --- (In reply to Jonathan Wakely from comment #4) > Because the warning isn't controlled by the -Wpacked option. If it was, it > would say [-Wpacked] after the warning. I think that's a bug, every warning > should be co

[Bug c++/79307] New: g++ misses warning for reference on temporary that invokes undefined behaviour

2017-01-31 Thread steven.spark at gmail dot com
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: steven.spark at gmail dot com Target Milestone: --- I thought (something like) this was fixed in bug 986 Code: struct TestRefInt { TestRefInt(const int& a) :

[Bug c++/79307] g++ misses warning for reference on temporary that invokes undefined behaviour

2017-02-01 Thread steven.spark at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79307 --- Comment #4 from Szikra --- > This is bug 44974. > > > Possible duplicate of bug #44859 or bug #51270. > > Looks more like bug 49974 to me. > > *** This bug has been marked as a duplicate of bug 44974 *** Hi you are right, my first example

[Bug c++/49974] missing warning for indirectly returning reference to local/temporary

2017-02-02 Thread steven.spark at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49974 --- Comment #8 from Szikra --- (In reply to Marc Glisse from comment #7) > We currently warn on all the examples involving X, with -O2. We don't for Y, > we might if there was a caller and the dangling reference was used there... Hi, I assume yo

[Bug c/61813] New: __attribute__((__packed__)) does not pack struct containing uint16_t with uint32_t

2014-07-15 Thread steven.spark at gmail dot com
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: steven.spark at gmail dot com Created attachment 33125 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33125&action=edit preprocessed bugreport_packed.c Te