[Bug target/92395] m68k-linux-gnu-gcc generates wrong code when the -mshort option is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92395 Eero Tamminen changed: What|Removed |Added CC||eerott at gmail dot com --- Comment #10

[Bug middle-end/44848] Bogus "array subscript is below array bounds" with loops

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44848 --- Comment #4 from Eero Tamminen --- (In reply to Richard Biener from comment #1) > This is the same as PR43270 (and the fix for it cures it). > > *** This bug has been marked as a duplicate of 43270 *** Current status is still NEW, but there's

[Bug c/48091] New: No warning when given function arguments mismatch earlier, old style K&R function definition

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48091 Summary: No warning when given function arguments mismatch earlier, old style K&R function definition Product: gcc Version: 4.4.5 Status: UNCONFIRMED Severity: normal

[Bug c/48091] No warning when given function arguments mismatch earlier, old style K&R function definition

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48091 --- Comment #2 from Eero Tamminen 2011-03-17 21:08:41 UTC --- (In reply to comment #1) > That's how K&R works. The function definition isn't a prototype. Why that would be a valid excuse not to give a warning when function call either doesn't m

gcc-bugs@gcc.gnu.org

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48091 Eero Tamminen changed: What|Removed |Added Summary|No warning when given |No warning when given |

[Bug c/48091] No warning when given function arguments mismatch earlier function definition which GCC assumes to be K&R, even with --std=c99 -pedantic

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48091 Eero Tamminen changed: What|Removed |Added Summary|No warning when given |No warning when given |

[Bug target/96532] [m68k] gcc 10.x generates calls to memset even for very small amounts

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96532 Eero Tamminen changed: What|Removed |Added CC||eerott at gmail dot com --- Comment #7