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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200708070504.l7754KIr004277@bongo.freakout.de>
Date:	Tue, 7 Aug 2007 07:04:20 +0200 (CEST)
From:	Axel Reinhold <axel@...akout.de>
To:	Willy Tarreau <w@....eu>
CC:	Segher Boessenkool <segher@...nel.crashing.org>,
	"H. Peter Anvin" <hpa@...or.com>, Axel Reinhold <axel@...akout.de>,
	linux-kernel@...r.kernel.org
Subject: 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/