Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI wrt direction flag

[H.J. Lu]

On Thu, Mar 6, 2008 at 9:06 AM, H. Peter Anvin <hpa@xxxxxxxxx> wrote:
>
> H.J. Lu wrote:
>  > On Thu, Mar 6, 2008 at 8:23 AM, Jakub Jelinek <jakub@xxxxxxxxxx> 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.
>  >
>
>  Not a fix, an (optional) workaround for a system bug.
>

So that is the bug in the Linux kernel. Since fixing kernel is much easier
than providing a workaround in compilers, I think kernel should be fixed
and no need for icc/gcc fix.


H.J.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/