On Sat, Oct 10, 2020, 8:16 AM Sebastian Huber wrote:
> Module:rtems
> Branch:master
> Commit:bc7ac71f8aaaff0c73469246c526741ec5b181ed
> Changeset:
> http://git.rtems.org/rtems/commit/?id=bc7ac71f8aaaff0c73469246c526741ec5b181ed
>
> Author:Frank Kühndel
> Date: Mon Oct 5 16:
On Sat, Oct 10, 2020, 10:47 AM Richi Dubey wrote:
> Hi Mr. Huber,
>
> Thanks for checking in.
>
> I suggested to enable your new scheduler implementation as the default
>> to check if it is in line with the standard schedulers. I would first
>> get some high level data. Select a BSP with good tes
On Sat, Oct 10, 2020 at 8:13 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 10/10/2020 15:11, Sebastian Huber wrote:
>
> > Hello Kinsey,
> >
> > the new aarch64/a53_ilp32_qemu produces a lot of warnings like this:
> >
> > ../../../testsuites/psxtests/psxhdrs/math/truncl.c:45:
Hi Mr. Huber,
Thanks for checking in.
I suggested to enable your new scheduler implementation as the default
> to check if it is in line with the standard schedulers. I would first
> get some high level data. Select a BSP with good test results on a
> simulator (for example sparc/leon3 or arm/rea
On 10/10/2020 15:11, Sebastian Huber wrote:
Hello Kinsey,
the new aarch64/a53_ilp32_qemu produces a lot of warnings like this:
../../../testsuites/psxtests/psxhdrs/math/truncl.c:45:12: warning:
implicit declaration of function 'truncl'
[-Wimplicit-function-declaration]
../../../testsuites/ps
Hello Kinsey,
the new aarch64/a53_ilp32_qemu produces a lot of warnings like this:
../../../testsuites/psxtests/psxhdrs/math/truncl.c:45:12: warning:
implicit declaration of function 'truncl' [-Wimplicit-function-declaration]
../../../testsuites/psxtests/psxhdrs/math/truncl.c:45:12: warning:
i
Hello Richi,
I suggested to enable your new scheduler implementation as the default
to check if it is in line with the standard schedulers. I would first
get some high level data. Select a BSP with good test results on a
simulator (for example sparc/leon3 or arm/realview_pbx_a9_qemu). Run the
Hello Alan,
On 09/10/2020 22:35, Alan Cudmore wrote:
After doing a lot of tracing through my application, it looks like
malloc_info works fine before we start our cFS application, but it
blocks after the cFS is initialized. This suggests some sort of memory
corruption.
I started by instrumenting
