http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59219
Richard Biener changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #5 from Richard Biener
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59219
--- Comment #4 from Martin Sebor ---
I understand. The current semantics of __builtin__xxx_chk are to:
a) check the constraints of the xxx function at compile time, and
b) diagnose constraint violations detected in (a) and call __xxx_chk, or
c) e
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59219
--- Comment #3 from Richard Biener ---
But if you are using __builtin__xxx_chk you are using a builtin and thus
are required to follow the builtins semantic. You can use __memcpy_chk
instead (but you won't get the optimization to memcpy for unkno
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59219
--- Comment #2 from Martin Sebor ---
I'm suggesting that when -fno-builtin is used, __builtin___memcpy_chk (and
other __bultin_xxx_chk) invocations that are determined not to exceed the size
of the buffer boundaries expand to a call to memcpy inst
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59219
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
