[Bug c++/61372] Add warning to detect noexcept functions that might throw [-Wnoexcept-mismatch]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61372 --- Comment #11 from David Crocker --- I've been bitten by this several times. In the absence of support for this type of checking in GCC I added exception checking to our own homebrew static analysis tool. It's already detected three situations

[Bug target/96882] Wrong assembly code generated with arm-none-eabi-gcc -flto -mfloat-abi=hard options

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96882 --- Comment #11 from David Crocker --- As the master branch was updated a year ago according to comment 10, does this mean that there is now a stable release of gcc that incudes the patch?

[Bug target/105523] Wrong warning array subscript [0] is outside array bounds

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523 David Crocker changed: What|Removed |Added CC||dcrocker at eschertech dot com

[Bug c++/48379] -Wdouble-promotion warns for promotion by varargs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48379 David Crocker changed: What|Removed |Added CC||dcrocker at eschertech dot com

[Bug target/96882] Wrong assembly code generated with arm-none-eabi-gcc -flto -mfloat-abi=hard options

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96882 David Crocker changed: What|Removed |Added CC||dcrocker at eschertech dot com

[Bug other/99486] New: Feature request: -fstack-check option for embedded processors

Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: dcrocker at eschertech dot com Target Milestone: --- The -fstack-check option merely adds code to probe the end of the new stack and relies on the hardware and operating system

[Bug c/47781] warnings from custom printf format specifiers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47781 David Crocker changed: What|Removed |Added CC||dcrocker at eschertech dot com

[Bug c++/61372] Add warning to detect noexcept functions that might throw

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61372 --- Comment #5 from David Crocker --- You seem to be assuming that C++ exceptions can propagate through functions compiled with a C compiler. On most platforms, they normally cannot, because a C compiler does not produce the information needed fo

[Bug c++/61372] Add warning to detect noexcept functions that might throw

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61372 --- Comment #3 from David Crocker --- (In reply to Jonathan Wakely from comment #2) > extern "C" functions can throw, so it would be wrong to unconditionally > assume they can't. True, you can write an extern "C" function that throws. But does i

[Bug c++/61372] Add warning to detect noexcept functions that might throw

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61372 David Crocker changed: What|Removed |Added CC||dcrocker at eschertech dot com

[Bug c++/79189] Poor code generation when using stateless lambda instead of normal function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79189 David Crocker changed: What|Removed |Added CC||dcrocker at eschertech dot com