Re: [PATCH 1/2] kbuild: Remove '-mno-global-merge'

2022-03-31 Thread Sedat Dilek
On Thu, Mar 31, 2022 at 5:37 PM Nathan Chancellor wrote: > > On Thu, Mar 31, 2022 at 09:11:12AM +0200, Sedat Dilek wrote: > > On Thu, Mar 31, 2022 at 5:27 AM Nathan Chancellor wrote: > > > > > > This flag is specific to clang, where it is only used by the 32-bit and > > > 64-bit ARM backends. In

Re: [PATCH 1/2] kbuild: Remove '-mno-global-merge'

2022-03-31 Thread Nathan Chancellor
On Thu, Mar 31, 2022 at 09:11:12AM +0200, Sedat Dilek wrote: > On Thu, Mar 31, 2022 at 5:27 AM Nathan Chancellor wrote: > > > > This flag is specific to clang, where it is only used by the 32-bit and > > 64-bit ARM backends. In certain situations, the presence of this flag > > will cause a warning

Re: [PATCH 1/2] kbuild: Remove '-mno-global-merge'

2022-03-31 Thread Sedat Dilek
On Thu, Mar 31, 2022 at 5:27 AM Nathan Chancellor wrote: > > This flag is specific to clang, where it is only used by the 32-bit and > 64-bit ARM backends. In certain situations, the presence of this flag > will cause a warning, as shown by commit 6580c5c18fb3 ("um: clang: Strip > out -mno-global-

[PATCH 1/2] kbuild: Remove '-mno-global-merge'

2022-03-30 Thread Nathan Chancellor
This flag is specific to clang, where it is only used by the 32-bit and 64-bit ARM backends. In certain situations, the presence of this flag will cause a warning, as shown by commit 6580c5c18fb3 ("um: clang: Strip out -mno-global-merge from USER_CFLAGS"). Since commit 61163efae020 ("kbuild: LLVML