[Bug c/114366] New: computed labels do not reflect true values of instruction pointer ranges when function is inlined

2024-03-16 Thread godmar at gmail dot com via Gcc-bugs
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: godmar at gmail dot com Target Milestone: --- Created attachment 57718 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57718&action=edit using

[Bug tree-optimization/105051] consider not combining malloc + memset to calloc when inside calloc itself

2022-03-25 Thread godmar at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105051 --- Comment #4 from Godmar Back --- Don't let perfect be the enemy of good. IMO, the detection doesn't need to be perfect in the sense of not having false negatives. All 3 bug reports of the calloc implementations you broke called malloc + mem

[Bug tree-optimization/105051] consider not combining malloc + memset to calloc when inside calloc itself

2022-03-24 Thread godmar at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105051 --- Comment #2 from Godmar Back --- Thank you for your reply. To make sure I understand, the only work-around is to completely disable all builtins (as in -fno-builtin), or is using `-fno-builtin-memset` as I proposed sufficient? I'm not sur

[Bug tree-optimization/105051] New: consider not combining malloc + memset to calloc when inside calloc itself

2022-03-24 Thread godmar at gmail dot com via Gcc-bugs
: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: godmar at gmail dot com Target Milestone: --- gcc 8.5.0 (and later) just broke our 18-year-old calloc implementation, which goes like this: void * calloc

[Bug c/99588] New: variable set but not used warning on static _Atomic assignment

2021-03-14 Thread godmar at gmail dot com via Gcc-bugs
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: godmar at gmail dot com Target Milestone: --- A student shared this program with me: #include #include void test() { static _Atomic int x = 0; printf("%d\n", x += 1); }

[Bug c++/70555] lambda capture of multi-dimensional VLA

2018-09-20 Thread godmar at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70555 --- Comment #11 from Godmar Back --- I have attached a test case where capture of multidimensional VLA results in internal compiler error: in expand_expr_real_1, at expr.c:9908 I do not know if this is a duplicate of this bug or a separate bug

[Bug c++/70555] lambda capture of multi-dimensional VLA

2018-09-20 Thread godmar at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70555 Godmar Back changed: What|Removed |Added CC||godmar at gmail dot com --- Comment #10