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 besides -Os (since b
On Monday 31 December 2012, Riku Voipio wrote:
> It's not good enough - the __u64 and friends are used elsewhere in the
> fuse code. However just pulling in linux/types.h as done in out OE
> overlay is good enough:
>
> http://git.linaro.org/gitweb?p=openembedded/meta-aarch64.git;a=blob;f=recipes-s
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
> from fuse build failure (
> https://bugs.launchpad.net/linaro-oe/+bug/1087757 ) and the same fuse
> co
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
On Friday 17 June 2011, Michael Hope wrote:
> Hi Paolo. I've had a look into this and updated the ticket. The
> problem is due to a change in behaviour between 4.5 and 4.6 when
> accessing strcuts marked with __attribute__((packed)). 4.5 would do a
> word-wise access where 4.6 assumes the worst
On Wednesday 09 February 2011 20:25:32 Will Deacon wrote:
> > - Why is architecture 0x4 not supported? This seems to be the variant of
> > the v7 debug architecture with memory-mapped registers. Apparently the
> > IGEP only supports this version ... Do you know what the
> > Beagle-/Pandaboard an
On Wednesday 06 October 2010, Steve Langasek wrote:
> It sounds like what you need for this is a multilib-enabled armel compiler
> build, that includes a libgcc build for ARMv7 as well as separate libgcc
> builds for whichever other ARM targets you're after. You should coordinate
> this with Marci
