lkml.org 
[lkml]   [2020]   [Jul]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: linux-next: Tree for Jul 10
From
Date
On 7/12/20 7:19 PM, Randy Dunlap wrote:
> On 7/12/20 3:01 PM, Stephen Rothwell wrote:
>> Hi Andy,
>>
>> On Sun, 12 Jul 2020 18:56:04 +0300 Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>>>
>>> On Fri, Jul 10, 2020 at 06:33:18PM +1000, Stephen Rothwell wrote:
>>>>
>>>> Changes since 20200709:
>>>
>>> I can't build it on Debian with Sparse enabled
>>>
>>> CC init/main.o
>>> init/main.c:760:20: warning: no previous prototype for ‘mem_encrypt_init’ [-Wmissing-prototypes]
>>> 760 | void __init __weak mem_encrypt_init(void) { }
>>> | ^~~~~~~~~~~~~~~~
>>> CHECK /home/andy/prj/linux-topic-uart/init/main.c
>>> include/linux/compiler.h:309:16: error: typename in expression
>>> include/linux/compiler.h:309:16: error: Expected ) in function call
>>> include/linux/compiler.h:309:16: error: got :
>>> ...
>>> (All READ_ONCE() entries fail)
>>>
>>> Is it known issue?
>>
>> Not that I am aware of at the moment. Does next-20200709 work? Does
>> Linus' tree work? The only obvious thing I can think of is commit
>
> I'm hitting this same thing on 5.8-rc5. (x86_64)
>
>
>> 6ec4476ac825 ("Raise gcc version requirement to 4.9")
>>
>> The commmit message says:
>>
>> Using _Generic also means that you will need to have a very recent
>> version of 'sparse', but thats easy to build yourself, and much less of
>> a hassle than some old gcc version can be.

OK, no problems, newer sparse fixes it.

--
~Randy

\
 
 \ /
  Last update: 2020-07-13 04:27    [W:0.065 / U:0.808 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site