[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2019-09-28 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 Martin Sebor changed: What|Removed |Added Keywords||diagnostic Status|NEW

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2019-09-27 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 Eric Gallager changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #1

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-06-11 Thread dcb314 at hotmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 --- Comment #16 from David Binderman --- Created attachment 30287 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30287&action=edit C++ source code Latest version understands NUM1.NUM2, 53 formatting specifiers and a bunch of prefixes like %#

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-03-08 Thread dcb314 at hotmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 --- Comment #15 from David Binderman 2013-03-08 08:48:47 UTC --- Created attachment 29615 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29615 C++ source code This one now understands 40 common formats and can properly interpret f

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-14 Thread dcb314 at hotmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 --- Comment #14 from David Binderman 2013-02-14 19:06:54 UTC --- Created attachment 29453 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29453 C++ source code Old version understood about a dozen formats, this later version under

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-07 Thread dcb314 at hotmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 --- Comment #13 from David Binderman 2013-02-07 21:21:56 UTC --- Created attachment 29391 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29391 C++ source code This code doesn't understand all sprintf % specifiers. It is future w

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-07 Thread dcb314 at hotmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 --- Comment #12 from David Binderman 2013-02-07 21:19:15 UTC --- I coded up some of my ideas into the attached C++ source code. Then I modified builtins.c and did a bootstrap. My small patch seems to be working well. I'm sure someone

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-06 Thread dcb314 at hotmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 --- Comment #11 from David Binderman 2013-02-06 18:47:37 UTC --- >It isn't that easy. For %'s you really have to parse all the characters after >% and figure out where the format specifier ends. Agreed. But it doesn't have to be perfect

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-06 Thread fweimer at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 Florian Weimer changed: What|Removed |Added CC||fweimer at redhat dot com ---

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-06 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 --- Comment #9 from Jakub Jelinek 2013-02-06 13:46:05 UTC --- 1) this is -D_FORTIFY_SOURCE warning, you can invent other warnings elsewhere 2) with -D_FORTIFY_SOURCE, e.g. sprintf is an inline function, so the FE sees it as a call to an in

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-06 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 --- Comment #8 from Manuel López-Ibáñez 2013-02-06 13:39:32 UTC --- (In reply to comment #7) > Because object sizes are finalized only during the objsz pass, after lots of > optimization passes. Note, as I said earlier, what matters most is tha

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-06 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 --- Comment #7 from Jakub Jelinek 2013-02-06 13:25:29 UTC --- Because object sizes are finalized only during the objsz pass, after lots of optimization passes. Note, as I said earlier, what matters most is that the check is performed at r

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-06 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 Manuel López-Ibáñez changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Commen

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-06 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Co

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-06 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 --- Comment #4 from Richard Biener 2013-02-06 12:21:12 UTC --- (In reply to comment #3) > Code is (maybe_emit_sprintf_chk_warning): > > /* If the format doesn't contain % args or %%, we know its size. */ > if (strchr (fmt_str, targ

[Bug middle-end/54582] gap in FORTIFY checking of buffer lengths

2013-02-06 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54582 Richard Biener changed: What|Removed |Added Component|c |middle-end Severity|m