[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wj1bhyhuJbA5_UbqAnbjqA_hSrmZFqCQrhJ=44P--T4vQ@mail.gmail.com>
Date: Wed, 5 Aug 2020 11:01:40 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Marc Zyngier <maz@...nel.org>,
open list <linux-kernel@...r.kernel.org>,
Shuah Khan <shuah@...nel.org>, patches@...nelci.org,
lkft-triage@...ts.linaro.org,
Ben Hutchings <ben.hutchings@...ethink.co.uk>,
linux- stable <stable@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Guenter Roeck <linux@...ck-us.net>, Willy Tarreau <w@....eu>,
Grygorii Strashko <grygorii.strashko@...com>
Subject: Re: [PATCH 5.7 0/6] 5.7.14-rc1 review
On Wed, Aug 5, 2020 at 10:39 AM Naresh Kamboju
<naresh.kamboju@...aro.org> wrote:
>
> [ sorry if it is not interesting ! ]
It's a bit interesting only because it is so odd.
> While building with old gcc-7.3.0 the build breaks for arm64
> whereas build PASS on gcc-8, gcc-9 and gcc-10.
Can you double-check that your gcc-7.3 setup is actually building the same tree?
Yeah, I know that's a slightly strange thing to ask, but your build
log really looks very odd. There should be nothing in that error that
is in any way compiler version specific.
Sure, we may have some header that checks the compiler version and
does something different based on that, and I guess that could be
going on. Except I don't even find anything remotely like that
anywhere. I do find some compiler version tests, but most ofd them
would trigger for all those compiler versions
Or is there perhaps some other configuration difference?
Linus
Powered by blists - more mailing lists