Re: [PATCH] tools/gnu: Enable LTO in RSB tools

On 16/6/2022 8:41 am, Joel Sherrill wrote: > On Wed, Jun 15, 2022 at 5:29 PM Chris Johns > wrote: > > On 15/6/2022 10:58 pm, Joel Sherrill wrote: > > What's the problem with enabling LTO support in the tools by default? > > None that I know of and this patch

Re: [PATCH] tools/gnu: Enable LTO in RSB tools

On Wed, Jun 15, 2022 at 5:29 PM Chris Johns wrote: > On 15/6/2022 10:58 pm, Joel Sherrill wrote: > > What's the problem with enabling LTO support in the tools by default? > > None that I know of and this patch enables the support by default. The RSB > incorrectly supported the configure

Re: [PATCH] tools/gnu: Enable LTO in RSB tools

On 15/6/2022 10:58 pm, Joel Sherrill wrote: > What's the problem with enabling LTO support in the tools by default? None that I know of and this patch enables the support by default. The RSB incorrectly supported the configure `--enable-lto` option. That option controls the host build and when

Re: [PATCH 1/3] bsp/aarch64: Flush the cache before invalidating it

Looks good. On 6/13/2022 20:39, chr...@rtems.org wrote: From: Chris Johns - Any page tables need to be flushed if the cache is enabled. Disabling the cache may only be available in secure mode. --- bsps/aarch64/include/bsp/aarch64-mmu.h | 3 ++- 1 file changed, 2 insertions(+), 1

Re: [PATCH 3/3] aarch64/gicv3: Remove accesses to secure registers

On 6/15/2022 09:51, Gedare Bloom wrote: On Tue, Jun 14, 2022 at 6:56 PM Chris Johns wrote: On 14/6/2022 11:44 pm, Gedare Bloom wrote: On Mon, Jun 13, 2022 at 7:39 PM wrote: From: Chris Johns --- bsps/include/dev/irq/arm-gicv3.h | 18 +++--- 1 file changed, 15 insertions(+),

Re: [PATCH 2/3] bsp/versal: Support more than 4G of RAM

On 6/15/2022 09:48, Gedare Bloom wrote: This was copied from the ZynqMP, should that also use a 64-bit value for the ram length? Probably any 64-bit architecture should do so? I'd agree with that. Kinsey ___ devel mailing list devel@rtems.org

Re: Porting PPS API support to RTEMS 5

This may be a better question to pose to users@ ml On Mon, Jun 13, 2022 at 8:10 AM wrote: > > Hello everyone, > > > > I ported the PPS API support from RTEMS 6 to RTEMS 5 and wanted to ask if > somebody is interest to have the changes in the upstream. If yes, I can > submit the patches. > > >

Re: [PATCH 3/5] bsps/stm32h7: allow config and usage of QSPI memory on stm32h757i-eval BSP

On Wed, Jun 15, 2022 at 9:00 AM Gedare Bloom wrote: > > On Fri, Jun 10, 2022 at 6:49 AM Karel Gardas wrote: > > > > The QSPI memory is initialized and used only when the BSP configure file > > sets QSPI memory size to non-zero value. Currently QSPI is run in memory > > mapped mode which allows

Re: [PATCH 3/5] bsps/stm32h7: allow config and usage of QSPI memory on stm32h757i-eval BSP

On Fri, Jun 10, 2022 at 6:49 AM Karel Gardas wrote: > > The QSPI memory is initialized and used only when the BSP configure file > sets QSPI memory size to non-zero value. Currently QSPI is run in memory > mapped mode which allows future RTEMS binary linkage and upload into QSPI > memory. > >

Re: [PATCH 3/5] cpukit/libmd/md5.c: fix warning

On Thu, Jun 9, 2022 at 12:09 AM Sebastian Huber wrote: > > On 08/06/2022 18:09, Joel Sherrill wrote: > > > > On Wed, Jun 8, 2022, 10:45 AM Gedare Bloom > > wrote: > > > > Does this code have an upstream? > > > > > > I tried to find it. Maybe whoever added it has

Re: [PATCH 3/3] aarch64/gicv3: Remove accesses to secure registers

On Tue, Jun 14, 2022 at 6:56 PM Chris Johns wrote: > > On 14/6/2022 11:44 pm, Gedare Bloom wrote: > > On Mon, Jun 13, 2022 at 7:39 PM wrote: > >> > >> From: Chris Johns > >> > >> --- > >> bsps/include/dev/irq/arm-gicv3.h | 18 +++--- > >> 1 file changed, 15 insertions(+), 3

Re: [PATCH 2/3] bsp/versal: Support more than 4G of RAM

This was copied from the ZynqMP, should that also use a 64-bit value for the ram length? Probably any 64-bit architecture should do so? On Tue, Jun 14, 2022 at 6:40 PM Chris Johns wrote: > > On 15/6/2022 2:43 am, Joel Sherrill wrote: > > OK but the commit message could be a bit more

[PATCH] sppps01: Add test case for early returns of pps_event()

--- testsuites/sptests/sppps01/init.c | 42 +++ 1 file changed, 42 insertions(+) diff --git a/testsuites/sptests/sppps01/init.c b/testsuites/sptests/sppps01/init.c index 996a3a1e16..ee3fe1645b 100644 --- a/testsuites/sptests/sppps01/init.c +++

Re: [PATCH] tools/gnu: Enable LTO in RSB tools

What's the problem with enabling LTO support in the tools by default? Using it is a different matter. --joel On Wed, Jun 15, 2022, 7:20 AM wrote: > From: Chris Johns > > --- > source-builder/config/binutils-2-1.cfg | 6 +- > source-builder/config/gcc-common-1.cfg | 10 +++--- > 2

Enable LTO support in RTEMS tools

This patch enables LTO support in RTWMS tools. It is not used unless you build and link apps with LTO options and link. I will look at adding a config.ini option to build RTEMS with the LTO options. Chris ___ devel mailing list devel@rtems.org

[PATCH] tools/gnu: Enable LTO in RSB tools

From: Chris Johns --- source-builder/config/binutils-2-1.cfg | 6 +- source-builder/config/gcc-common-1.cfg | 10 +++--- 2 files changed, 4 insertions(+), 12 deletions(-) diff --git a/source-builder/config/binutils-2-1.cfg b/source-builder/config/binutils-2-1.cfg index