Re: How to add a dependency on start.o to the test executables in waf?

On 25/10/2019 07:33, Chris Johns wrote: On 25/10/19 4:26 pm, Sebastian Huber wrote: On 25/10/2019 07:18, Sebastian Huber wrote: How can I add a dependency on start.o to the test executables? I tried several variants of bld.add_manual_dependency(), but nothing worked. I am not sure, I would

Re: How to add a dependency on start.o to the test executables in waf?

On 25/10/19 4:26 pm, Sebastian Huber wrote: > On 25/10/2019 07:18, Sebastian Huber wrote: >>> How can I add a dependency on start.o to the test executables? I tried several variants of bld.add_manual_dependency(), but nothing worked. >>> >>> I am not sure, I would need to have a clo

Re: How to add a dependency on start.o to the test executables in waf?

On 25/10/2019 07:18, Sebastian Huber wrote: How can I add a dependency on start.o to the test executables? I tried several variants of bld.add_manual_dependency(), but nothing worked. I am not sure, I would need to have a close look at how the test stuff is being put together. I cannot see

Re: How to add a dependency on start.o to the test executables in waf?

On 25/10/2019 03:41, Chris Johns wrote: On 25/10/19 12:12 am, Sebastian Huber wrote: Hello, I have a problem in the new build system, which I am not able to solve with my novice waf knowledge. You can check out the prototype with these steps: git clone git://git.rtems.org/sebh/rtems.git cd rt

RE: [PATCH v5] riscv: add freedom E310 Arty A7 bsp

Hi, Thanks everyone for support and guidance. @Sebastian Huber I will do documentation soon. - Pragnesh -Original Message- From: Sebastian Huber Sent: 23 October 2019 11:46 To: Pragnesh Patel ; rtems-de...@rtems.org; Sachin Ghadi Subject: Re: [PATCH v5] riscv: add freedom E310 Arty

Re: xilinx_zynq_zc702 vs. xilinx_zynq_zc706 memory map

On 25/10/19 8:41 am, Chris Johns wrote: > On 24/10/19 7:50 pm, Sebastian Huber wrote: >> On 24/10/2019 03:41, Jonathan Brandmeyer wrote: >>> On Wed, Oct 23, 2019 at 6:04 AM Thomas Doerfler >>> wrote: Hi, most likely the RAM areas have been mapped to the lowest-possible non

Re: How to add a dependency on start.o to the test executables in waf?

On 25/10/19 12:12 am, Sebastian Huber wrote: > Hello, > > I have a problem in the new build system, which I am not able to solve with my > novice waf knowledge. > > You can check out the prototype with these steps: > > git clone git://git.rtems.org/sebh/rtems.git > cd rtems > git checkout --trac

[PATCH 1/3] sb/build: Add -E to '%source setup' to handle tar dependency errors.

From: Chris Johns Tar on Windows raises an error if a symlink appears before the target. Windows needs the target to exist before a link can be created. This patch adds support via the -E option to catch the error and rerun the tar command a second time. The symlink should work as the target shou

[PATCH 3/3] rtems/llvm: Add support to build llvm on Windows.

From: Chris Johns --- source-builder/config/llvm-common-1.cfg | 36 + 1 file changed, 25 insertions(+), 11 deletions(-) diff --git a/source-builder/config/llvm-common-1.cfg b/source-builder/config/llvm-common-1.cfg index c75769f..629d2bf 100644 --- a/source-builder/conf

[PATCH 2/3] sb/windows: Add the optional cmake command.

From: Chris Johns --- source-builder/sb/windows.py | 1 + 1 file changed, 1 insertion(+) diff --git a/source-builder/sb/windows.py b/source-builder/sb/windows.py index 0f93b6c..199a6b8 100644 --- a/source-builder/sb/windows.py +++ b/source-builder/sb/windows.py @@ -102,6 +102,7 @@ def load():

Re: [PATCH v2] [rsb] Update Spike build

On 24/10/19 7:57 pm, Hesham Almatary wrote: > Latest Spike integrated fesvr in its source directory, so there > is no separate fesvr anymore. Nice. Building and installing fesvr was a little unusual. Chris ___ devel mailing list devel@rtems.org http://

Re: xilinx_zynq_zc702 vs. xilinx_zynq_zc706 memory map

On 24/10/19 7:50 pm, Sebastian Huber wrote: > On 24/10/2019 03:41, Jonathan Brandmeyer wrote: >> On Wed, Oct 23, 2019 at 6:04 AM Thomas Doerfler >> wrote: >>> >>> Hi, >>> >>> most likely the RAM areas have been mapped to the lowest-possible >>> non-NULL address, and they can be mapped to an addres

Re: [PATCH v2 2/5] riscv: Address differences in the linkerscript between GNU LD and LLVM/LLD

On 25/10/19 8:36 am, Chris Johns wrote: > On 25/10/19 1:25 am, Hesham Almatary wrote: >> LLVM/LLD does not support STARTUP and ALIGN_WITH_INPUT directives that >> GNU LD support. INPUT and ALIGN(8) are supported by LLVM/LLD and can >> replace the unsupported STARTUP/ALIGN_WITH_INPUT directives. >

Re: [PATCH v2 2/5] riscv: Address differences in the linkerscript between GNU LD and LLVM/LLD

On 25/10/19 1:25 am, Hesham Almatary wrote: > LLVM/LLD does not support STARTUP and ALIGN_WITH_INPUT directives that > GNU LD support. INPUT and ALIGN(8) are supported by LLVM/LLD and can > replace the unsupported STARTUP/ALIGN_WITH_INPUT directives. Does "INPUT and ALIGN(8)" work with GCC? That

Re: RTEMS Google Code-In 2019

Hello everyone! I am interested in mentoring for Google Code-In 2019. -- Vaibhav Gupta On Fri, Oct 25, 2019, 1:28 AM Vijay Kumar Banerjee wrote: > > > > On Fri, Oct 25, 2019 at 12:58 AM Himanshu Sekhar Nayak < > himanshuwindows...@gmail.com> wrote: > >> Hi guys, >> >> So the Org. application s

Re: RTEMS Google Code-In 2019

On Fri, Oct 25, 2019 at 12:58 AM Himanshu Sekhar Nayak < himanshuwindows...@gmail.com> wrote: > Hi guys, > > So the Org. application submission is still going on and the last date is > 28th Oct. As far as I know, we have collected 3 mentors and we gonna need > more for mentoring students. Also men

RTEMS Google Code-In 2019

Hi guys, So the Org. application submission is still going on and the last date is 28th Oct. As far as I know, we have collected 3 mentors and we gonna need more for mentoring students. Also mentoring and organizing the tasks for young generations is amazing and it will benefit the Org. too. So if

Re: RFC: Building RTEMS/RISC-V with LLVM/Clang

Hi Sebastian, On Thu, 24 Oct 2019 at 12:48, Sebastian Huber wrote: > > Hello, > > I work currently on a new build system based on waf and Doorstop. It > would be good to have the clang support at the top level of the build > system. Doing this for the current build system is probably a waste of >

[PATCH v2 5/5] riscv: Add new BSP cfg variants to be built with llvm/clang

--- bsps/riscv/riscv/config/rv32i_clang.cfg | 14 ++ bsps/riscv/riscv/config/rv32iac_clang.cfg| 14 ++ bsps/riscv/riscv/config/rv32im_clang.cfg | 14 ++ bsps/riscv/riscv/config/rv32imac_clang.cfg | 14 ++ bsps/riscv/riscv/config/rv32im

[PATCH v2 4/5] riscv: Add new offending input sections to the linker script

--- bsps/riscv/shared/start/linkcmds.base.in | 5 + 1 file changed, 5 insertions(+) diff --git a/bsps/riscv/shared/start/linkcmds.base.in b/bsps/riscv/shared/start/linkcmds.base.in index 7d6a23cde0..d921e29fe4 100644 --- a/bsps/riscv/shared/start/linkcmds.base.in +++ b/bsps/riscv/shared/star

[PATCH v2 1/5] riscv: Generate linkcmds.base from the shared linkcmds.base.in

This commit moves the existing linkcmds.base to linkcmds.base.in in order to make it configurable by autotools. --- bsps/riscv/shared/start/{linkcmds.base => linkcmds.base.in} | 0 c/src/lib/libbsp/riscv/riscv/Makefile.am| 2 +- c/src/lib/libbsp/riscv/riscv/configure.ac

[PATCH v2 2/5] riscv: Address differences in the linkerscript between GNU LD and LLVM/LLD

LLVM/LLD does not support STARTUP and ALIGN_WITH_INPUT directives that GNU LD support. INPUT and ALIGN(8) are supported by LLVM/LLD and can replace the unsupported STARTUP/ALIGN_WITH_INPUT directives. The commit conditionally adds the supported directive that linkers can understand depending on th

[PATCH v2 3/5] riscv: Add NOLOAD directive to the .work section

ld.lld defaults .work to PROGBITS otherwise --- bsps/riscv/shared/start/linkcmds.base.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bsps/riscv/shared/start/linkcmds.base.in b/bsps/riscv/shared/start/linkcmds.base.in index 857bf2dabd..7d6a23cde0 100644 --- a/bsps/riscv/sha

How to add a dependency on start.o to the test executables in waf?

Hello, I have a problem in the new build system, which I am not able to solve with my novice waf knowledge. You can check out the prototype with these steps: git clone git://git.rtems.org/sebh/rtems.git cd rtems git checkout --track origin/build ./waf bsp_defaults --rtems-bsps=sparc > bsps.in

Re: RFC: Building RTEMS/RISC-V with LLVM/Clang

Hello, I work currently on a new build system based on waf and Doorstop. It would be good to have the clang support at the top level of the build system. Doing this for the current build system is probably a waste of time. In general, I am fine with your changes. It would be great if you cou

Re: [RFC PATCH 2/5] riscv: Address differences in the linkerscript between GNU LD and LLVM/LLD

On 24/10/2019 11:15, Hesham Almatary wrote: On Thu, 24 Oct 2019 at 09:58, Sebastian Huber wrote: On 23/10/2019 15:44, Hesham Almatary wrote: LLVM/LLD does not support STARTUP and ALIGN_WITH_INPUT directives that GNU LD support. INPUT and ALIGN(8) are supported by LLVM/LLD and can replace the

Re: [RFC PATCH 1/5] riscv: Generate linkcmds.base from the shared linkcmds.base.in

On Thu, 24 Oct 2019 at 09:59, Sebastian Huber wrote: > > On 23/10/2019 15:44, Hesham Almatary wrote: > > This commit moves the existing linkcmds.base to linkcmds.base.in > > in order to make it configurable by autotools. > > This file is also used by the grisp BSP, does it work after this change?

Re: [RFC PATCH 5/5] riscv: Add a new BSP cfg variant to be built with llvm/clang

On Thu, 24 Oct 2019 at 09:55, Sebastian Huber wrote: > > On 23/10/2019 15:44, Hesham Almatary wrote: > > +# Clang-related flags > > +CPU_CFLAGS += -target riscv64-unknown-rtems6 -D__rtems__ > > --sysroot=$(NEWLIB_SYSROOT) > > Was clang configured to support this target? If yes, then why doesn't i

Re: [RFC PATCH 2/5] riscv: Address differences in the linkerscript between GNU LD and LLVM/LLD

On Thu, 24 Oct 2019 at 09:58, Sebastian Huber wrote: > > On 23/10/2019 15:44, Hesham Almatary wrote: > > LLVM/LLD does not support STARTUP and ALIGN_WITH_INPUT directives that > > GNU LD support. INPUT and ALIGN(8) are supported by LLVM/LLD and can > > replace the unsupported STARTUP/ALIGN_WITH_IN

Re: [RFC PATCH 1/5] riscv: Generate linkcmds.base from the shared linkcmds.base.in

On 23/10/2019 15:44, Hesham Almatary wrote: This commit moves the existing linkcmds.base to linkcmds.base.in in order to make it configurable by autotools. This file is also used by the grisp BSP, does it work after this change? -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4

[PATCH v2] [rsb] Update Spike build

Latest Spike integrated fesvr in its source directory, so there is no separate fesvr anymore. Also use a revision of Spike that fixes the file permissions when getting installed. --- bare/config/devel/spike-1.1.0.cfg | 12 ++-- source-builder/config/spike-1-1.cfg | 22 ++

Re: [RFC PATCH 2/5] riscv: Address differences in the linkerscript between GNU LD and LLVM/LLD

On 23/10/2019 15:44, Hesham Almatary wrote: LLVM/LLD does not support STARTUP and ALIGN_WITH_INPUT directives that GNU LD support. INPUT and ALIGN(8) are supported by LLVM/LLD and can replace the unsupported STARTUP/ALIGN_WITH_INPUT directives. The commit conditionally adds the supported directi

Re: [RFC PATCH 5/5] riscv: Add a new BSP cfg variant to be built with llvm/clang

On 23/10/2019 15:44, Hesham Almatary wrote: +# Clang-related flags +CPU_CFLAGS += -target riscv64-unknown-rtems6 -D__rtems__ --sysroot=$(NEWLIB_SYSROOT) Was clang configured to support this target? If yes, then why doesn't it define __rtems__ automatically? -- Sebastian Huber, embedded brai

Re: [RFC PATCH 4/5] riscv: Add new offending input sections to the linker script

On 23/10/2019 15:44, Hesham Almatary wrote: --- bsps/riscv/shared/start/linkcmds.base.in | 5 + 1 file changed, 5 insertions(+) diff --git a/bsps/riscv/shared/start/linkcmds.base.in b/bsps/riscv/shared/start/linkcmds.base.in index 7d6a23cde0..d921e29fe4 100644 --- a/bsps/riscv/shared/sta

Re: xilinx_zynq_zc702 vs. xilinx_zynq_zc706 memory map

On 24/10/2019 03:41, Jonathan Brandmeyer wrote: On Wed, Oct 23, 2019 at 6:04 AM Thomas Doerfler wrote: Hi, most likely the RAM areas have been mapped to the lowest-possible non-NULL address, and they can be mapped to an address boundary matching the RAM size. zc702 has a 1MByte ram, mapped to