This is the mail archive of the gcc@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] | |
On Thu, Mar 6, 2008 at 8:23 AM, Jakub Jelinek <jakub@redhat.com> wrote:On Thu, Mar 06, 2008 at 07:50:12AM -0800, H. Peter Anvin wrote: > H.J. Lu wrote: > >I agree with it. There is no right or wrong here Let's start from > >scratch and figure out > >what is the best way to handle this, assuming we are defining a new psABI.
BTW, just tested icc and icc doesn't generate cld either (so it matches the new gcc behavior). char buf1[32], buf2[32]; void bar (void); void foo (void) { __builtin_memset (buf1, 0, 32); bar (); __builtin_memset (buf2, 0, 32); }
Icc follows the psABI. If we are saying icc/gcc 4.3 need a fix, we'd better define a new psABI first.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |