Re: RTEMS 5 gcc-fb371a33fa6 vs gcc-9.2.0

2019-08-14 Thread Chris Johns
On 15/8/19 4:10 pm, Sebastian Huber wrote: > - Am 15. Aug 2019 um 0:43 schrieb Chris Johns chr...@rtems.org: > >> On 14/8/19 5:38 pm, Sebastian Huber wrote: >>> On 14/08/2019 09:25, Sebastian Huber wrote: On 14/08/2019 09:09, Chris Johns wrote: > On 14/8/19 4:52 pm, Sebastian Hub

Re: [PATCH v2] rtems-record: New program

2019-08-14 Thread Chris Johns
On 15/8/19 4:05 pm, Sebastian Huber wrote: > - Am 15. Aug 2019 um 2:09 schrieb Chris Johns chr...@rtems.org: > >> On 14/8/19 3:19 pm, Sebastian Huber wrote: >>> On 14/08/2019 03:57, Chris Johns wrote: On 13/8/19 3:10 pm, Sebastian Huber wrote: > sorry for the rush, Sorry

Re: SPE Support

2019-08-14 Thread Sebastian Huber
- Am 15. Aug 2019 um 0:55 schrieb joel j...@rtems.org: > Hi > > Just thinking out loud. > > If the SPE continues to be supported by GCC, why can't we just have > spe as a separate CPU in the tree with all the build infrastructure > just reference PowerPC files as needed in their current loca

Re: RTEMS 5 gcc-fb371a33fa6 vs gcc-9.2.0

2019-08-14 Thread Sebastian Huber
- Am 15. Aug 2019 um 0:43 schrieb Chris Johns chr...@rtems.org: > On 14/8/19 5:38 pm, Sebastian Huber wrote: >> On 14/08/2019 09:25, Sebastian Huber wrote: >>> >>> On 14/08/2019 09:09, Chris Johns wrote: On 14/8/19 4:52 pm, Sebastian Huber wrote: > On 14/08/2019 08:52, Chris Johns wro

Re: [PATCH v2] rtems-record: New program

2019-08-14 Thread Sebastian Huber
- Am 15. Aug 2019 um 2:09 schrieb Chris Johns chr...@rtems.org: > On 14/8/19 3:19 pm, Sebastian Huber wrote: >> On 14/08/2019 03:57, Chris Johns wrote: >>> On 13/8/19 3:10 pm, Sebastian Huber wrote: sorry for the rush, >>> >>> Sorry for the delay, I have a client demo this week I am helpi

[PATCH v1] Add steps to test Newlib patch.

2019-08-14 Thread Vaibhav Gupta
Update the checksum to be used for the Newlib patches. Earlier it was msd5, but it is depreciated for security reasons. Now RSB accepts sha512. --- user/rsb/project-sets.rst | 41 +-- 1 file changed, 35 insertions(+), 6 deletions(-) diff --git a/user/rsb/projec

Fwd: [PATCH v1] Remove back-slash in 'pacman' command in 'PDF' section under Arch Linux (installation of Sphinx).

2019-08-14 Thread Vaibhav Gupta
--- README.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.txt b/README.txt index 3679d1d..1567be6 100644 --- a/README.txt +++ b/README.txt @@ -247,7 +247,7 @@ Sphinx: PDF: - # pacman -S texlive-bin texlive-core texlive-latexextra texlive-fontsextra \ + # pacman

[PATCH 1/2] sb/download: Add support for a base64 hash string

2019-08-14 Thread chrisj
From: Chris Johns --- source-builder/sb/download.py | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/source-builder/sb/download.py b/source-builder/sb/download.py index d8061e6..1fb0155 100644 --- a/source-builder/sb/download.py +++ b/source-builder/sb/download.py @

LibBSD master vs 5-freebsd12 TI frame buffer patches

2019-08-14 Thread Chris Johns
Hi, Currently the RSB libbsd package is building and installing LibBSD `master` and I was looking to move this to `5-freebsd12` to align it with the needs of a release. >From what I can see important patches are on both branches which is great. >Thanks. I am wondering about the recent GSoC com

Re: [PATCH v2] rtems-record: New program

2019-08-14 Thread Chris Johns
On 14/8/19 3:19 pm, Sebastian Huber wrote: > On 14/08/2019 03:57, Chris Johns wrote: >> On 13/8/19 3:10 pm, Sebastian Huber wrote: >>> sorry for the rush, >> >> Sorry for the delay, I have a client demo this week I am helping with. >> >>> but what do you think of this patch? >> >> Why not C++? The

Re: [PATCH] dtc.bset: update to 1.4.1 to match qemu

2019-08-14 Thread Joel Sherrill
On Wed, Aug 14, 2019, 6:02 PM Chris Johns wrote: > On 15/8/19 8:50 am, Joel Sherrill wrote: > > On Wed, Aug 14, 2019 at 5:27 PM Chris Johns wrote: > >> > >> On 15/8/19 8:08 am, Joel Sherrill wrote: > >>> qemu-couverture.bset explicitly has 1.4.1. > >> > >> OK. > >> > >>> qemu.bset doesn't list d

Re: [PATCH] dtc.bset: update to 1.4.1 to match qemu

2019-08-14 Thread Chris Johns
On 15/8/19 8:50 am, Joel Sherrill wrote: > On Wed, Aug 14, 2019 at 5:27 PM Chris Johns wrote: >> >> On 15/8/19 8:08 am, Joel Sherrill wrote: >>> qemu-couverture.bset explicitly has 1.4.1. >> >> OK. >> >>> qemu.bset doesn't list dtc at all. No idea why not. >> >> Because you cannot build dtc on Min

SPE Support

2019-08-14 Thread Joel Sherrill
Hi Just thinking out loud. If the SPE continues to be supported by GCC, why can't we just have spe as a separate CPU in the tree with all the build infrastructure just reference PowerPC files as needed in their current location? I can see a need to copy/move a bsp.h and perhaps, score/cpu/spe/in

Re: [PATCH] dtc.bset: update to 1.4.1 to match qemu

2019-08-14 Thread Joel Sherrill
On Wed, Aug 14, 2019 at 5:27 PM Chris Johns wrote: > > On 15/8/19 8:08 am, Joel Sherrill wrote: > > qemu-couverture.bset explicitly has 1.4.1. > > OK. > > > qemu.bset doesn't list dtc at all. No idea why not. > > Because you cannot build dtc on MinGW and I doubt you ever will be able to. > Here >

Re: RTEMS 5 gcc-fb371a33fa6 vs gcc-9.2.0

2019-08-14 Thread Chris Johns
On 14/8/19 5:38 pm, Sebastian Huber wrote: > On 14/08/2019 09:25, Sebastian Huber wrote: >> >> On 14/08/2019 09:09, Chris Johns wrote: >>> On 14/8/19 4:52 pm, Sebastian Huber wrote: On 14/08/2019 08:52, Chris Johns wrote: On ARM a breaking change in compiler options is necessary.

Re: [PATCH] dtc.bset: update to 1.4.1 to match qemu

2019-08-14 Thread Chris Johns
On 15/8/19 8:08 am, Joel Sherrill wrote: > qemu-couverture.bset explicitly has 1.4.1. OK. > qemu.bset doesn't list dtc at all. No idea why not. Because you cannot build dtc on MinGW and I doubt you ever will be able to. Here the MSYS2 package is used. I cannot remember the specifics. > But qemu

Re: littleVGL now supports FreeBSD framebuffer

2019-08-14 Thread Chris Johns
On 15/8/19 2:07 am, Vijay Kumar Banerjee wrote: > I wrote a patch for lv_drivers repository to support FreeBSD framebuffer > in fbdev, which they merged to the master today. Well done, that is great. > I have tested > the driver to be working with an app that I wrote on FreeBSD and > tested it o

Re: Checksum Error on Leon3 Qemu patches

2019-08-14 Thread Joel Sherrill
On Wed, Aug 14, 2019 at 4:42 PM Chris Johns wrote: > > On 15/8/19 12:46 am, Joel Sherrill wrote: > > > > Qemu isn't building due to a checksum error. > > > > These patches are at gaisler.org. I don't know where to move them but > > eventually they should be moved. > > You can post them to qemu's p

Re: [PATCH] dtc.bset: update to 1.4.1 to match qemu

2019-08-14 Thread Joel Sherrill
qemu-couverture.bset explicitly has 1.4.1. qemu.bset doesn't list dtc at all. No idea why not. But qemu-git-1.cfg has a dtc submodule of qemu pulled out of git so I guess qemu.bset is implicitly getting that. Clear as mud to me. On Wed, Aug 14, 2019 at 4:40 PM Chris Johns wrote: > > Which qemu?

Re: Checksum Error on Leon3 Qemu patches

2019-08-14 Thread Chris Johns
On 15/8/19 12:46 am, Joel Sherrill wrote: > > Qemu isn't building due to a checksum error. > > These patches are at gaisler.org. I don't know where to move them but > eventually they should be moved. You can post them to qemu's patchworks and then get them from there. The RSB supports fetching f

Re: [PATCH] dtc.bset: update to 1.4.1 to match qemu

2019-08-14 Thread Chris Johns
Which qemu? On 15/8/19 1:36 am, j...@rtems.org wrote: > From: Joel Sherrill > > --- > bare/config/devel/dtc.bset | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/bare/config/devel/dtc.bset b/bare/config/devel/dtc.bset > index d701f93..54521f6 100644 > --- a/bare/config/

Re: fenv on RISC-V

2019-08-14 Thread Jiri Gaisler
Having said that, I will check if the generation of FP exception flag for RISC-V in sis are as accurate as for SPARC. Generating the wrong flags could cause the type of failures we are seeing ... On 8/14/19 10:42 PM, Jiri Gaisler wrote: > Interesting. I can confirm that the griscv bsp is using h

Re: fenv on RISC-V

2019-08-14 Thread Jiri Gaisler
Interesting. I can confirm that the griscv bsp is using hard floats and doubles, it is compiled with -march=rv32imafd -mabi=ilp32d. The paranoia benchmark runs successfully and uses float instructions and registers. The sis simulator emulates all float and double instructions as define in the RI

Re: RTEMS Source Builder failed for MX Linux

2019-08-14 Thread Himanshu Sekhar Nayak
Hi Chris, Finally RTEMS build run for MX Linux. I will soon release the patch after testing it. Thanks Himanshu ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

fenv on RISC-V

2019-08-14 Thread Joel Sherrill
Hi I emailed Jim Wilson of SiFive and got a quick response. Much thanks to him and this is his reply: == I don't have any embedded hardware that I can use for testing. I just have linux and simulators (qemu, gdb sim). I haven't seen gcc testsuite failures related to fenv, but no

GSoC Final report review

2019-08-14 Thread Vijay Kumar Banerjee
Hello all, I have prepared a draft for the GSoC final report. It would be nice to have some review on it before I push it to the blog. The google docs link [1] contains a paste from the .md file that will be converted to html for the blog so the formatting got messed up in the word file and the li

littleVGL now supports FreeBSD framebuffer

2019-08-14 Thread Vijay Kumar Banerjee
Hello all, I wrote a patch for lv_drivers repository to support FreeBSD framebuffer in fbdev, which they merged to the master today. I have tested the driver to be working with an app that I wrote on FreeBSD and tested it on Beaglebone black image 12-STABLE. I intend to write an RSB recipe to bui

[PATCH 2/2] spike.bset: Add dtc

2019-08-14 Thread joel
From: Joel Sherrill --- bare/config/devel/spike.bset | 1 + 1 file changed, 1 insertion(+) diff --git a/bare/config/devel/spike.bset b/bare/config/devel/spike.bset index c7a6340..76392f7 100644 --- a/bare/config/devel/spike.bset +++ b/bare/config/devel/spike.bset @@ -4,4 +4,5 @@ %define rele

[PATCH] dtc.bset: update to 1.4.1 to match qemu

2019-08-14 Thread joel
From: Joel Sherrill --- bare/config/devel/dtc.bset | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bare/config/devel/dtc.bset b/bare/config/devel/dtc.bset index d701f93..54521f6 100644 --- a/bare/config/devel/dtc.bset +++ b/bare/config/devel/dtc.bset @@ -4,4 +4,4 @@ %defin

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Vaibhav Gupta
On Wed, Aug 14, 2019 at 8:56 PM Hesham Almatary wrote: > On Wed, 14 Aug 2019 at 16:18, Vaibhav Gupta > wrote: > > > > > > > > On Wed, Aug 14, 2019, 8:09 PM Joel Sherrill wrote: > >> > >> On Wed, Aug 14, 2019 at 9:35 AM Vaibhav Gupta > wrote: > >> > > >> > You are also getting same error :( > >

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Hesham Almatary
On Wed, 14 Aug 2019 at 16:18, Vaibhav Gupta wrote: > > > > On Wed, Aug 14, 2019, 8:09 PM Joel Sherrill wrote: >> >> On Wed, Aug 14, 2019 at 9:35 AM Vaibhav Gupta >> wrote: >> > >> > You are also getting same error :( >> > I thought problem is with my system/laptop and was trying to correct >>

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Vaibhav Gupta
On Wed, Aug 14, 2019, 8:09 PM Joel Sherrill wrote: > On Wed, Aug 14, 2019 at 9:35 AM Vaibhav Gupta > wrote: > > > > You are also getting same error :( > > I thought problem is with my system/laptop and was trying to correct > things. > > Should we take the discussion to newlib? > > I would like

Checksum Error on Leon3 Qemu patches

2019-08-14 Thread Joel Sherrill
Hi Qemu isn't building due to a checksum error. These patches are at gaisler.org. I don't know where to move them but eventually they should be moved. checksums: 0001-LEON3-Add-emulation-of-AMBA-plug-play.patch: 1162bfb7b5839237803356e5fb6efaafdec5b9d2df9d23de42c86d48c5e35327 =

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Joel Sherrill
On Wed, Aug 14, 2019 at 9:35 AM Vaibhav Gupta wrote: > > You are also getting same error :( > I thought problem is with my system/laptop and was trying to correct things. > Should we take the discussion to newlib? I would like Jiri and Hesham to chime in on the next step. I don't know the RISC-V

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Vaibhav Gupta
You are also getting same error :( I thought problem is with my system/laptop and was trying to correct things. Should we take the discussion to newlib? Vaibhav Gupta On Wed, Aug 14, 2019 at 7:51 PM Joel Sherrill wrote: > > I ran it on sis built from the git repository. Unfortunately, the outpu

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Joel Sherrill
I ran it on sis built from the git repository. Unfortunately, the output doesn't match that I got on Linux. = $ ~/sis-riscv/install/bin/sis -riscv -gdb SIS - SPARC/RISCV instruction simulator 2.17, copyright Jiri Gaisler 2019 Bug-reports to j...@gaisler.se RISCV e

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Vaibhav Gupta
On Wed, Aug 14, 2019 at 6:22 PM Hesham Almatary wrote: > On Sun, 11 Aug 2019 at 16:49, Vaibhav Gupta > wrote: > > > > Configure command I used to build BSP: > > == > > $ /home/varodek/development/rtems/kernel/rtems/configure > --prefix=/home/varodek/de

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Hesham Almatary
On Sun, 11 Aug 2019 at 16:49, Vaibhav Gupta wrote: > > Configure command I used to build BSP: > == > $ /home/varodek/development/rtems/kernel/rtems/configure > --prefix=/home/varodek/development/rtems/5 --enable-maintainer-mode > --target=riscv-rtems5

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Vaibhav Gupta
So I cloned the 'sis' repository and build it locally: $ git clone git://git.rtems.org/sis.git . . On one terminal I was running sis: $ ~/development/sis/sis -riscv nouartrx -gdb . . . . On another terminal I did: $ riscv-rtems5-gdb psxfenv01.exe Reading symbols from psxfenv01.exe...done. (gdb) t

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Vaibhav Gupta
Hello I get following errors: = $ riscv-rtems5-sis -riscv -nouartrx -gdb SIS - SPARC/RISCV instruction simulator 2.13, copyright Jiri Gaisler 2019 Bug-reports to j...@gaisler.se unknown option -riscv usage: sis [-uart1 uart_device1] [-uar

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

2019-08-14 Thread Joel Sherrill
Thank you. Do you see anything wrong with the riscv fenv implementation? His program runs under Linux and hangs on both Qemu and sis. On Wed, Aug 14, 2019, 2:18 AM Jiri Gaisler wrote: > I have attached the sis manual. Page 17: > > "SIS can be connected to gdb through a network socket using the

Re: RTEMS 5 gcc-fb371a33fa6 vs gcc-9.2.0

2019-08-14 Thread Sebastian Huber
On 14/08/2019 09:25, Sebastian Huber wrote: On 14/08/2019 09:09, Chris Johns wrote: On 14/8/19 4:52 pm, Sebastian Huber wrote: On 14/08/2019 08:52, Chris Johns wrote: On ARM a breaking change in compiler options is necessary. What options are these? ARM changed the FPU options in GCC 8 and

Re: RTEMS 5 gcc-fb371a33fa6 vs gcc-9.2.0

2019-08-14 Thread Sebastian Huber
On 14/08/2019 09:09, Chris Johns wrote: On 14/8/19 4:52 pm, Sebastian Huber wrote: On 14/08/2019 08:52, Chris Johns wrote: On ARM a breaking change in compiler options is necessary. What options are these? ARM changed the FPU options in GCC 8 and later. Also this seems back to front to me

Re: Bug Reporting Page

2019-08-14 Thread Sebastian Huber
On 14/08/2019 09:13, Chris Johns wrote: On 14/8/19 3:39 pm, Sebastian Huber wrote: I completed my work with moving the bug reporting information to the user manual. Please have a look at the changed New Ticket page: https://devel.rtems.org/wiki/NewTicket Why remove the information from the p

Re: Bug Reporting Page

2019-08-14 Thread Chris Johns
On 14/8/19 3:39 pm, Sebastian Huber wrote: > I completed my work with moving the bug reporting information to the user > manual. Please have a look at the changed New Ticket page: > > https://devel.rtems.org/wiki/NewTicket > Why remove the information from the page that guides a user? Chris ___

Re: RTEMS 5 gcc-fb371a33fa6 vs gcc-9.2.0

2019-08-14 Thread Chris Johns
On 14/8/19 4:52 pm, Sebastian Huber wrote: > On 14/08/2019 08:52, Chris Johns wrote: > On ARM a breaking change in compiler options is necessary. What options are these? >>> ARM changed the FPU options in GCC 8 and later. >>> Also this seems back to front to me. Should all hosts be on