This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] don't bzero->memset if cfun is memset


>>>>> "Mark" == Mark Mitchell <mark@codesourcery.com> writes:

 Mark> What we do know is that, in general, the user wants bzero
 Mark> converted to memset (or else she would have used -fno-builtin).

The documentation for -fno-builtin gives no hint of this.  It only
talks about replacing calls to "standard" function names by inline
code that has the same effect, and the need for this switch if you
want to set breakpoints in those library functions or replace them by
specialized ones.

It says nothing about gcc rewriting a call to "foo" into a call to
"bar".  Is there a reason why gcc *has* to do this?

       paul


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]