On Tue, Feb 7, 2017 at 10:51 AM, J. Tang wrote:
>
>> On 2017-02-06, at 01:35, Bin Meng wrote:
>>
>> +Simon,
>>
>> I do not have a GCC5 toolchain to test this. I suspect this is only
>> exposed with GCC5, or GCC 5.4? Is there any parameter to control the
>> behavior?
>
> I observed a similar behav
> On 2017-02-06, at 01:35, Bin Meng wrote:
>
> +Simon,
>
> I do not have a GCC5 toolchain to test this. I suspect this is only
> exposed with GCC5, or GCC 5.4? Is there any parameter to control the
> behavior?
I observed a similar behavior with GCC 5.3.
As an experiment, I disabled CONFIG_CC_
+Simon,
On Sun, Feb 5, 2017 at 11:54 PM, J. Tang wrote:
> On latest master (commit 0ff27d), when using the stock qemu-x86_defconfig, it
> is possible to build an invalid U-Boot. I traced the issue to
> arch/x86/cpu/interrupts.c. The problem is that cpu_init_interrupts() assumes
> that each IRQ
On latest master (commit 0ff27d), when using the stock qemu-x86_defconfig, it
is possible to build an invalid U-Boot. I traced the issue to
arch/x86/cpu/interrupts.c. The problem is that cpu_init_interrupts() assumes
that each IRQ entry consumes the same number of bytes. Depending upon the
comp
4 matches
Mail list logo
