Hi Masahiro, On 3/6/20 11:37 AM, Masahiro Yamada wrote: > On Fri, Mar 6, 2020 at 3:36 PM Amit Daniel Kachhap <amit.kachhap@xxxxxxx> wrote: >> >> From: Vincenzo Frascino <vincenzo.frascino@xxxxxxx> >> >> Currently kconfig does not have a feature that allows to detect if the >> used assembler supports a specific compilation option. >> >> Introduce 'as-option' to serve this purpose in the context of Kconfig: >> >> config X >> def_bool $(as-option,...) >> >> Cc: Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx> >> Cc: linux-kbuild@xxxxxxxxxxxxxxx >> Acked-by: Masahiro Yamada <masahiroy@xxxxxxxxxx> >> Signed-off-by: Vincenzo Frascino <vincenzo.frascino@xxxxxxx> >> Signed-off-by: Amit Daniel Kachhap <amit.kachhap@xxxxxxx> >> --- >> Changes since v5: >> * More descriptions for using /dev/zero. > > > FYI: > > This has been fixed: > > https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3c968de5c7d1719b2f9b538f2f7f5f5922e5f311 > > > So, this will not be a problem for the > future release of binutils. > > Anyway, we need to take care of the released ones, > so I am fine with /dev/zero. > Thank you for letting us know. I did not realize it was a compiler issue otherwise I would have reported it. I thought it was a mechanism to prevent people from trashing their code, but thinking at it more carefully, for devices does not make sense hence it is good that there is a fix already. [...] -- Regards, Vincenzo
