Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3

According to Willy Tarreau:
> > >Well, top-level assembly is usually nasty.  Setting the section in the
> > >assembly statement as you said is probably the only thing you *can* do.
> > 

I do not understand the details of the discussion, but isn't the
fact, that there is more than one way for the compiler to produce
"correct" code of the nasty statements, also a "timebomb" for
other projects - especially for Linux 2.6?

Axel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
    • From: Willy Tarreau <[email protected]>

• References:
  • Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
    • From: Willy Tarreau <[email protected]>

• Prev by Date: IPsec IPv4 over IPv6 Problem: No route to host
• Next by Date: Re: [PATCH] ifdef struct task_struct::security
• Previous by thread: Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
• Next by thread: Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]