On Thu, Jan 14, 2021 at 12:33 PM Jakub Jelinek wrote:
>
> On Thu, Jan 14, 2021 at 10:52:24AM -0800, sunil.k.pandey via Gcc-patches
> wrote:
> > On Linux/x86_64,
>
> It breaks x86_64-linux build pretty much everywhere.
> libatomic (but as well libgomp and libitm) uses -march=i486 in certain
On Thu, Jan 14, 2021 at 10:52:24AM -0800, sunil.k.pandey via Gcc-patches wrote:
> On Linux/x86_64,
It breaks x86_64-linux build pretty much everywhere.
libatomic (but as well libgomp and libitm) uses -march=i486 in certain cases.
While for --with-arch or --with-arch_32 configured compilers it
On Linux/x86_64,
77d372abec0fbf2cfe922e3140ee3410248f979e is the first bad commit
commit 77d372abec0fbf2cfe922e3140ee3410248f979e
Author: H.J. Lu
Date: Thu Jan 14 05:56:46 2021 -0800
x86: Error on -fcf-protection with incompatible target
caused build failure when configured with:
