------- Comment #2 from xinliangli at gmail dot com 2008-03-12 06:22 ------- (In reply to comment #1) > Subject: Re: New: value profiling support for memOps such as memcpy > > > > Sent from my iPhone > > On Mar 11, 2008, at 22:32, "xinliangli at gmail dot com" > <[EMAIL PROTECTED] > > wrote: > > > Value profiling on the length parameters of memset, memcpy, memmove, > > strncmp, > > strncpy, memcmp, etc can be guide the inline expansion strategy for > > those > > calls. As an example, very large sized memcpy may prefer non- > > temporal memory > > move etc. > > This is already done for 4.3.0. >
Yes, looks like it is done for memcpy, memset, bzero, etc, but not strncmp, memcmp, memmove, strncpy etc. > > > > > > > > > -- > > Summary: value profiling support for memOps such as memcpy > > Product: gcc > > Version: 4.4.0 > > Status: UNCONFIRMED > > Severity: enhancement > > Priority: P3 > > Component: middle-end > > AssignedTo: unassigned at gcc dot gnu dot org > > ReportedBy: xinliangli at gmail dot com > > > > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35543 > > > -- xinliangli at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|value profiling support for |Add more strOp for value |memOps such as memcpy |profiling http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35543
