Re: [PATCH RSB 4/4] qemu-couverture: update to qemu-stable-4.0.0

On Fri, Apr 10, 2020 at 9:53 AM Gedare Bloom wrote: > How was it tested? > > I ran coverage analysis on leon3-qemu-cov, it's working fine with this qemu-couverture build. > On Thu, Apr 9, 2020 at 2:22 PM Vijay Kumar Banerjee > wrote: > > > > --- > > bare/config/devel/qemu-couverture-git-1.cfg

[PATCH 8/9] [waf]: Fix ptimer.h -> timer.h header name in yml file

--- spec/build/cpukit/RTEMS-BUILD-CPUKIT-LIBRTEMSCPU.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/build/cpukit/RTEMS-BUILD-CPUKIT-LIBRTEMSCPU.yml b/spec/build/cpukit/RTEMS-BUILD-CPUKIT-LIBRTEMSCPU.yml index 1d956173f0..2b473acb51 100644 --- a/spec/build/cpukit/RTEM

[PATCH 9/9] [waf] Add an option to build C++ sample applications

Defaults to false --- .../testsuites/RTEMS-BUILD-TEST-GRPTOP.yml| 1 + .../testsuites/RTEMS-BUILD-TEST-OPTCXX.yml| 20 +++ .../RTEMS-BUILD-TEST-SAMPLE-CDTEST.yml| 3 ++- .../RTEMS-BUILD-TEST-SAMPLE-FILEIO.yml| 3 ++- .../RTEMS-BUILD-TEST-SAMPLE-IOSTREAM.y

[PATCH 4/9] [waf] Fix assembling when compiling with Clang/LLVM

Currently waf_lib only knows about nasm and gas, and automatically sets the required flags for those. When building with Clang/LLVM it gets confused about the assembler and fails to add the appropriate flags. This commit adds such needed flags to be able to handle assembling .S files with Clang/LL

[PATCH 5/9] [waf] Add a new ARCH_BITS option to be used in Clang's -triple

--- .../cpukit/RTEMS-BUILD-CPUKIT-CPUOPTS.yml | 1 + .../cpukit/RTEMS-BUILD-CPUKIT-OPTARCHBITS.yml | 30 +++ 2 files changed, 31 insertions(+) create mode 100644 spec/build/cpukit/RTEMS-BUILD-CPUKIT-OPTARCHBITS.yml diff --git a/spec/build/cpukit/RTEMS-BUILD-CPUKIT-CPUOPTS.ym

[PATCH 0/0] Clang/LLVM for RTEMS Waf Build

Hello, The following set of patches are a few fixes and added support to build RTEMS with Clang/LLVM from the new Waf build system, with RISC-V as the main target architecture. Best, Hesham ___ devel mailing list devel@rtems.org http://lists.rtems.org/m

[PATCH 1/9] [waf] Fatal error if the compiler can't be found

Don't default to gcc if the compiler can't be found --- wscript | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/wscript b/wscript index b135da74be..c0a3fd31e8 100755 --- a/wscript +++ b/wscript @@ -1232,7 +1232,8 @@ def get_compiler(conf, cp, variant): value = no_uni

[PATCH 6/9] [waf][clang] Add required -target flag to ABI_FLAGS

--- spec/build/cpukit/RTEMS-BUILD-CPUKIT-OPTCLANG.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/spec/build/cpukit/RTEMS-BUILD-CPUKIT-OPTCLANG.yml b/spec/build/cpukit/RTEMS-BUILD-CPUKIT-OPTCLANG.yml index cac645e5ee..c5b218b5b1 100644 --- a/spec/build/cpukit/RTEMS-BUILD-CPUKIT-OPTCLAN

[PATCH 3/9] [waf] Move bsp_specs flag to GCC only file

--- spec/build/bsps/RTEMS-BUILD-BSP-OPTLDFLAGS.yml | 2 -- spec/build/cpukit/RTEMS-BUILD-CPUKIT-OPTGCC.yml | 6 ++ 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/spec/build/bsps/RTEMS-BUILD-BSP-OPTLDFLAGS.yml b/spec/build/bsps/RTEMS-BUILD-BSP-OPTLDFLAGS.yml index 75d4f6637f..

[PATCH 7/9] [waf] Add -I and -L flags to pkgconfig for Clang/LLVM

--- spec/build/bsps/RTEMS-BUILD-BSP-PKGCONFIG.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/build/bsps/RTEMS-BUILD-BSP-PKGCONFIG.yml b/spec/build/bsps/RTEMS-BUILD-BSP-PKGCONFIG.yml index aa8a874235..128cd7d302 100644 --- a/spec/build/bsps/RTEMS-BUILD-BSP-PKGCONFIG.y

[PATCH 2/9] [waf] Out COMPILER value from bsp_defaults for later confiugre

configure reads this from config.ini and uses it later. Otherwise, there is no other way to pass 'COMPILER' from bsp_defaults's options to configure and it's assigned None. --- wscript | 1 + 1 file changed, 1 insertion(+) diff --git a/wscript b/wscript index c0a3fd31e8..c763e214f6 100755 --- a/w

Re: [PATCH v2] bsp/raspberrypi: Fix build warnings.

This patch has been unnoticed for a while. If the lack of testing is what is stopping from pushing it I am happy to test it on real hardware. But I can't come up with a good methodology for testing it. My initial thoughts were to generate a GPIO interrupt with no ISR. This would cause the default

Re: [PATCH v2] bsp/raspberrypi: Fix build warnings.

Pushed. I'm sorry. It is surprising but working from home seems to create even more work than being in the office. I am swamped. :( --joel On Fri, Apr 10, 2020 at 7:59 AM Niteesh G. S. wrote: > This patch has been unnoticed for a while. > If the lack of testing is what is stopping from pushin

Re: [PATCH RSB 4/4] qemu-couverture: update to qemu-stable-4.0.0

I pushed this. Thanks. This was actually on the list in the back of my mind but never got a ticket. On Fri, Apr 10, 2020 at 5:24 AM Vijay Kumar Banerjee wrote: > > > On Fri, Apr 10, 2020 at 9:53 AM Gedare Bloom wrote: > >> How was it tested? >> >> I ran coverage analysis on leon3-qemu-cov, it

Re: [PATCH RSB 4/4] qemu-couverture: update to qemu-stable-4.0.0

On Fri, Apr 10, 2020, 7:03 PM Joel Sherrill wrote: > I pushed this. Thanks. This was actually on the list in the back of my > mind but never got a ticket. > > Thanks! Can you please also push the other 3 patches? The qemu-couverture build depends on them. > > > On Fri, Apr 10, 2020 at 5:24 AM Vi

Re: [PATCH 0/0] Clang/LLVM for RTEMS Waf Build

On Fri, Apr 10, 2020 at 7:24 AM suyash singh wrote: > Hello, > > As part of my proposed Gsoc, > > I am trying to integrate clang static analyzer and UBSan in rtems. > > Both of them work with the build process of a project > We should likely start a new thread for discussing the GSoC project.

Re: [PATCH v3] bsp/beagle: Update console to new Termios API.

Hello Niteesh, sorry for the late review. It somehow slipped my attention. Although I'm generally OK with it, my suggestion would be to move it after the release. It's a not strictly necessary change and therefore I don't want to potentially break stuff with it now. I added some comments below:

Clang with the new build system

I came to know about the new waf build system in RTEMS. How do I start to work on clang static analysis of BSPs with the new build system? ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: GCC 10 build status

Hello, I encountered also some new multiple definition errors. The reason for this is that GCC 10 defaults to -fno-common. This could likely also lead to issues in applications. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/l

Re: [PATCH 9/9] [waf] Add an option to build C++ sample applications

Hello, C++ tests should be disabled if the configure didn't find a C++ compiler. Do we have an architecture without C++ support from the compiler? ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH 7/9] [waf] Add -I and -L flags to pkgconfig for Clang/LLVM

Hello, On 10/04/2020 12:39, Hesham Almatary wrote: --- spec/build/bsps/RTEMS-BUILD-BSP-PKGCONFIG.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/build/bsps/RTEMS-BUILD-BSP-PKGCONFIG.yml b/spec/build/bsps/RTEMS-BUILD-BSP-PKGCONFIG.yml index aa8a874235..128cd7d302

Re: [PATCH 4/9] [waf] Fix assembling when compiling with Clang/LLVM

On 10/04/2020 12:39, Hesham Almatary wrote: Currently waf_lib only knows about nasm and gas, and automatically sets the required flags for those. When building with Clang/LLVM it gets confused about the assembler and fails to add the appropriate flags. This commit adds such needed flags to be a

Re: [PATCH v3] bsp/beagle: Update console to new Termios API.

On Fri, Apr 10, 2020 at 9:18 PM Christian Mauderer wrote: > Hello Niteesh, > > sorry for the late review. It somehow slipped my attention. > > Although I'm generally OK with it, my suggestion would be to move it > after the release. It's a not strictly necessary change and therefore I > don't wan

Re: [PATCH 1/9] [waf] Fatal error if the compiler can't be found

On 10/04/2020 12:39, Hesham Almatary wrote: Don't default to gcc if the compiler can't be found All options should have a default. I should be possible to build a BSP just with: [arch/bsp] ___ devel mailing list devel@rtems.org http://lists.rtems

Re: [PATCH 0/0] Clang/LLVM for RTEMS Waf Build

Hello Hesham, thanks for your patches. I checked in most of them. Some with slight modifications. I changed the RTEMS version to 6 and removed the bsp_specs. The latest unstable RTEMS 6 tools from the RSB are now required to work with the new build system and GCC. _

New Build System Update

Hello, I changed the RTEMS version to 6 and removed the bsp_specs in the branch with the new build system: https://git.rtems.org/sebh/rtems.git/log/?h=build The latest unstable RTEMS 6 tools from the RSB are now required to work with the new build system and GCC. __

Re: [PATCH 1/9] [waf] Fatal error if the compiler can't be found

Hello Sebastian, On Fri, 10 Apr 2020 at 20:23, Sebastian Huber wrote: > > On 10/04/2020 12:39, Hesham Almatary wrote: > > > Don't default to gcc if the compiler can't be found > > All options should have a default. I should be possible to build a BSP > just with: > > [arch/bsp] > This patch doesn

Re: [PATCH 1/9] [waf] Fatal error if the compiler can't be found

On 10/04/2020 22:38, Hesham Almatary wrote: Hello Sebastian, On Fri, 10 Apr 2020 at 20:23, Sebastian Huber wrote: On 10/04/2020 12:39, Hesham Almatary wrote: Don't default to gcc if the compiler can't be found All options should have a default. I should be possible to build a BSP just wit

Re: [PATCH 9/9] [waf] Add an option to build C++ sample applications

On Fri, 10 Apr 2020 at 19:07, Sebastian Huber wrote: > > Hello, > > C++ tests should be disabled if the configure didn't find a C++ > compiler. Do we have an architecture without C++ support from the compiler? > Having clang++ doesn't mean it can still compile C++ apps. Similar to having to build

Re: [PATCH 1/9] [waf] Fatal error if the compiler can't be found

I believe my other patch (that outputs COMPILER to config.ini) has hidden this issue. I was getting it when I specify --rtems-compiler=clang as in > ./waf bsp_defaults --rtems-bsps=rv64imafdc_medany --rtems-compiler=clang > > config.ini That didn't output COMPILER in config.ini. So during ./waf

Re: [PATCH 9/9] [waf] Add an option to build C++ sample applications

Also similar to the legacy autotools (--disable-cxx), users might want to disable building CXX apps from config.ini or the spec. On Fri, 10 Apr 2020 at 21:45, Hesham Almatary wrote: > > On Fri, 10 Apr 2020 at 19:07, Sebastian Huber > wrote: > > > > Hello, > > > > C++ tests should be disabled if

Re: [PATCH v4 0/3] [5-freebsd-12] Fix compilation for i386

Someone familiar with libbsd can review these for pushing. The main concern from my perspective would be the things under sys/net. On Thu, Apr 9, 2020 at 7:57 AM Jan Sommer wrote: > > This is the backport for the 5-freebsd-12 branch to make rtems-libbsd > compile for i386 again: > - It also int

Correct makefile configuration for test framework?

I encountered linkage error while building test using the test framework, in particular undefined reference to `_Stack_Space_size' undefined reference to `_Thread_Initial_thread_count' While building test file through the test framework my makefile configuration is ( I took the libtests/ttest01 co

Re: Correct makefile configuration for test framework?

> On 11-Apr-2020, at 11:37 AM, Utkarsh Rai wrote: > >  > I encountered linkage error while building test using the test framework, in > particular > undefined reference to `_Stack_Space_size' > undefined reference to `_Thread_Initial_thread_count' > > While building test file through the tes