On Fri, Nov 22, 2019 at 2:40 PM Adhemerval Zanella
wrote:
>
> Hi Arnd,
>
> I took a look on the stack usage issue in the kernel snippet you provided [1],
> and as you have noted the most impact indeed come from -ftree-ch optimization.
> It is enabled in all optimization levels
a_qPtrOBT2watYq_HA%40mail.gmail.com&forum_name=fuse-devel
>
> No response back yet,
>
The patch basically reverts back to the previous state from a few years ago. I
think
that is fine, but you seem to be missing the #include statement in the #else
path.
Arnd
__
t, hence the conflict that happens here but not on some other
architectures. Normally these don't conflict, since the "long long"
variant is only used for kernel interfaces.
I don't know why the fuse header does this, because it's otherwise
a straight copy of inclu
On Thursday 27 December 2012, Arnd Bergmann wrote:
> On Wednesday 19 December 2012, Riku Voipio wrote:
> > Hi,
> >
> > The following code fails to build with OE Aarch64 toolchain with
> > current kernel headers. While ugly, the code is a reduced testcase
> > fr
On Monday 20 June 2011, Nicolas Pitre wrote:
> On Mon, 20 Jun 2011, Arnd Bergmann wrote:
>
> > On Saturday 18 June 2011, Nicolas Pitre wrote:
> > Well, in case of readl/writel, we need the memory clobber for other reasons:
> > They might trigger a DMA operation, or the rea
On Saturday 18 June 2011, Nicolas Pitre wrote:
> On Fri, 17 Jun 2011, Arnd Bergmann wrote:
> I played with this a bit.
It looks like much more than a bit, thanks for the detailed analysis!
> I think that GCC might have improved on this
> front. It at least doesn't seem to
lly and
> then a long term plan worked out between the kernel and compiler.
>
> Arnd, do you want to pick up that thread? Both Ubuntu and Debian are
> now 4.6 based so this problem will come up more often. I think Patrik
> said there's a fix for this specific problem pending
hould be
> > using to verify GDB support is working?
>
> The simple rule is Cortex-A8 is unsupported and Cortex-A9 is supported.
> The A5 should work (untested) and the A15 will need a bit of hacking to
> get it supported.
Is that because A8 is memory mapped and A9 uses CP14, or
(big-endian, thumb 1,
hardfloat) that might need an extra multilib variant if we really
want them.
Arnd
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
linaro toolchain is currently very much usable to build a pre-v7
kernel and anything that uses -ffreestanding, and IMHO we should
try to keep it that way.
Would there be anything that we might want to build besides u-boot that
requires an matching libgcc but not also an matching
10 matches
Mail list logo
