Paolo Bonzini wrote:
> On 05/05/2018 19:22, Nadav Amit wrote:
>> Paolo Bonzini wrote:
>>
>>> -ftracer can duplicate asm blocks causing compilation to fail in
>>> noclone functions. For example, KVM declares a global variable
>>> in an asm like
>>>
>>> asm("2: ... \n
>>>.pushsection
On 05/05/2018 19:22, Nadav Amit wrote:
> Paolo Bonzini wrote:
>
>> -ftracer can duplicate asm blocks causing compilation to fail in
>> noclone functions. For example, KVM declares a global variable
>> in an asm like
>>
>>asm("2: ... \n
>> .pushsection data \n
>> .global vmx_r
Paolo Bonzini wrote:
> -ftracer can duplicate asm blocks causing compilation to fail in
> noclone functions. For example, KVM declares a global variable
> in an asm like
>
>asm("2: ... \n
> .pushsection data \n
> .global vmx_return \n
> vmx_return: .long 2b");
>
> a
Hi Paolo,
[auto build test WARNING on v4.6-rc1]
[also build test WARNING on next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Paolo-Bonzini/compiler-gcc-disable-ftracer-for-__noclo
-ftracer can duplicate asm blocks causing compilation to fail in
noclone functions. For example, KVM declares a global variable
in an asm like
asm("2: ... \n
.pushsection data \n
.global vmx_return \n
vmx_return: .long 2b");
and -ftracer causes a double declaration
5 matches
Mail list logo