Re: [PATCH] Fix --show-commands.

Am 06.06.2018 um 09:48 schrieb Christian Mauderer: > In the current version of libbsd, if the --show-commands option is used, > the cwd is passed as a Nod3. Popen does not work with that. Therefore > create a string from cwd if it isn't already. > --- > rtems.py | 2 ++ > 1 file changed, 2 inserti

Re: RISC-V tool chain

On 06/06/2018 19:57, Sebastian Huber wrote: > On 06/06/18 07:16, Sebastian Huber wrote: >> We could use an unofficial mirror on Github, e.g. >> >> https://codeload.github.com/bminor/binutils-gdb/tar.gz/c61b06a19a34baab66e3809c7b41b0c31009ed9f >> >> >> My main concern with using all these different

Re: [PATCH 3/6] shgen: Import from RTEMS

On 07/06/2018 16:11, Sebastian Huber wrote: > On 07/06/18 07:53, Chris Johns wrote: >> On 07/06/2018 15:39, Sebastian Huber wrote: >>> Corresponding RTEMS commit is 75933d5d25cd50f80162b7a0d2f66a5534e1763f. >>> >>> Update #3443. >>> --- >>>   misc/shgen/AUTHORS |   3 + >>>   misc/shgen/COPYING | 34

Re: configure/make with multiple jobs error?

On 08/06/2018 04:42, Gedare Bloom wrote: > OK, and I concur with your assessment. It worked a couple months ago. > I might try to bisect if I have time. I would bet something in our > scripts that changed during the source code reorg causes the problem. It should not be hard to find. Please raise

Re: [GSoC - x86_64 BSP] Using fPIC to compile RTEMS as a shared library

On 08/06/2018 01:50, Amaan Cheval wrote: > > Joel, Chris, I'd appreciate guidance on what I ought to work on next I would like to see the focus on the kernel context switcher, FPU support, and then interrupts so we have the basic drivers we need like a tick interrupt running. This assumes the l

Re: RISC-V tool chain

On 06/06/2018 19:37, Hesham Almatary wrote: > If pulling from external GitHub repos (i.e. not GNU) is an option, > then [1, 2] are very well-maintained and have any cutting-edge > changes that are supposed to be merged with GNU repos. SiFive's SDK, > FreeBSD and seL4 rely on riscv-tools and I alwa

Re: (release notes generator) How to convert python dictionary to release notes using sphinx?

On 08/06/2018 05:21, Joel Sherrill wrote: > On Thu, Jun 7, 2018 at 1:45 PM, Gedare Bloom > wrote: > > Hello Chris, Dannie, > > I am leaning toward a lighter method such as markdown for the release > notes. They are not necessary to be a beautifully formatted

Re: (release notes generator) How to convert python dictionary to release notes using sphinx?

Hi, I think Chris mentioned that the RSB has a Markdown implementation: https://git.rtems.org/rtems-source-builder/tree/source-builder/sb/markdown I am gonna use Markdown since it is good with everybody :) Best, Dannie On Thu, Jun 7, 2018 at 2:21 PM, Joel Sherrill wrote: > > > On Thu, Jun 7,

Re: error while building leon3 with gcov flags

On Fri, 8 Jun 2018, 01:09 Joel Sherrill, wrote: > Bringing in Krzysztof. Hoping he can get us on the right track here. > > I don't think you can run GcovData.cc independent of a covoar run. > Understood. > If you can figure out how to write a unit test that would be helpful. > Will try to do tha

Re: error while building leon3 with gcov flags

Bringing in Krzysztof. Hoping he can get us on the right track here. I don't think you can run GcovData.cc independent of a covoar run. If you can figure out how to write a unit test that would be helpful. On Thu, Jun 7, 2018 at 2:29 PM, Vijay Kumar Banerjee < vijaykumar9...@gmail.com> wrote: >

Re: error while building leon3 with gcov flags

Hello, I was looking into the code in GcovData.cc to see how it works and what it's doing, too me it looked like very messed up, I couldn't understand (yet) what it's trying to do. Is there some way I can manually run it for one file? Is there any place where I can read how it was intended to work

Re: (release notes generator) How to convert python dictionary to release notes using sphinx?

On Thu, Jun 7, 2018 at 1:45 PM, Gedare Bloom wrote: > Hello Chris, Dannie, > > I am leaning toward a lighter method such as markdown for the release > notes. They are not necessary to be a beautifully formatted document. > Some basic document sectioning, lists, and url support seems > sufficient

Re: Thoughts on Reusing FreeBSD msun tests

On Thu, Jun 7, 2018 at 2:02 PM, Gedare Bloom wrote: > Well, after this summer, maybe you can write a couple of > paravirtualized x86_64 BSPs to run under *nix, *BSD, MacOS, and > Windows to test newlib and rtems on native hosting. > I don't even know how to test newlib natively at this point. I

Re: Thoughts on Reusing FreeBSD msun tests

Well, after this summer, maybe you can write a couple of paravirtualized x86_64 BSPs to run under *nix, *BSD, MacOS, and Windows to test newlib and rtems on native hosting. On Thu, Jun 7, 2018 at 2:59 PM, Joel Sherrill wrote: > Sigh.. that makes things even more complex. > > As a general rule, we

Re: Thoughts on Reusing FreeBSD msun tests

Sigh.. that makes things even more complex. As a general rule, we probably should just set a goal to run newlib tests on an RTEMS BSP and help improve newlib's tests. --joel On Thu, Jun 7, 2018 at 1:40 PM, Gedare Bloom wrote: > Relatedly, you may also want to read through > https://sourceware.

Re: (release notes generator) How to convert python dictionary to release notes using sphinx?

Hello Chris, Dannie, I am leaning toward a lighter method such as markdown for the release notes. They are not necessary to be a beautifully formatted document. Some basic document sectioning, lists, and url support seems sufficient to me. This would also be easily parseable by other tools in case

Re: configure/make with multiple jobs error?

On Wed, Jun 6, 2018 at 11:12 PM, Chris Johns wrote: > On 07/06/2018 03:55, Gedare Bloom wrote: >> On Tue, Jun 5, 2018 at 9:02 PM, Chris Johns wrote: >>> On 31/5/18 2:56 am, Gedare Bloom wrote: >>> >>> Is this still only with a concurrent build? >>> >> >> I think this was without concurrent build.

Re: Thoughts on Reusing FreeBSD msun tests

Relatedly, you may also want to read through https://sourceware.org/ml/newlib/2017/msg01216.html On Wed, Jun 6, 2018 at 12:05 PM, Joel Sherrill wrote: > Hi > > I can't find this on FreeBSD head but it looks like a decent > set of tests for fenv and other libm functionality. > > http://web.mit.edu

Re: RISC-V tool chain

On Thu, Jun 7, 2018 at 2:25 AM, Sebastian Huber wrote: > On 06/06/18 09:34, Chris Johns wrote: >>> >>> We could use an unofficial mirror on Github, e.g. >>> >>> >>> https://codeload.github.com/bminor/binutils-gdb/tar.gz/c61b06a19a34baab66e3809c7b41b0c31009ed9f >>> >>> >>> My main concern with usin

Re: [PATCH] Adding tracing documentation in user manual

On Wed, Jun 6, 2018 at 5:24 AM, Vidushi Vashishth wrote: > > >>> I am just sending a revised version with incorporations of your >>> suggestions. I will create a fresh version 2 patch after everyone has >>> reviewed. >> >> >> If you send revised version, then please send them as a separate patch >

[PATCH] coverage : Add support to run coverage in supported bsp without extra options

Close #3440 --- tester/rt/coverage.py | 6 -- tester/rt/test.py | 15 ++- 2 files changed, 14 insertions(+), 7 deletions(-) diff --git a/tester/rt/coverage.py b/tester/rt/coverage.py index 54933d5..af24124 100644 --- a/tester/rt/coverage.py +++ b/tester/rt/coverage.py @@ -163

Re: [Tracing] Deciding the Yaml configuration for barectf input

On 07/06/18 11:31, Vidushi Vashishth wrote: Hi! Quick question. I tried to modify the printk trace generator to print the output traces into a text file instead of the console. On running the normal link and trace linker commands there are no compilation errors. However when I run the applica

[PATCH] build: Force warnings

Always append some standard warning flags. --- c/src/configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/c/src/configure.ac b/c/src/configure.ac index f4428ed221..7e4986e03d 100644 --- a/c/src/configure.ac +++ b/c/src/configure.ac @@ -100,7 +100,7 @@ RTEMS_PROG_CCAS R

Re: [Tracing] Deciding the Yaml configuration for barectf input

Hi! Quick question. I tried to modify the printk trace generator to print the output traces into a text file instead of the console. On running the normal link and trace linker commands there are no compilation errors. However when I run the application executable using GDB it says [Inferior 1 (pr

Re: [Tracing] Deciding the Yaml configuration for barectf input

Hi Sebastian. > I still have problems to see the big picture. Would it be possible to > implement both approaches using a simple example? I am working on the babeltrace approach and using the fileio test case to track entry and exit of malloc, calloc, realloc and free functions. I will have som

Re: [Tracing] Deciding the Yaml configuration for barectf input

Hello Vidushi, I still have problems to see the big picture. Would it be possible to implement both approaches using a simple example? On 06/06/18 19:31, Vidushi Vashishth wrote: Hi! I have written a blog post  (https://vidushivashishth.github.io/sixthpost/

[PATCH 2/2] powerpc: Fix ss555 build

The mpc555 define is provided via . It must not be used in cpukit header files. Update #3425. --- bsps/powerpc/ss555/include/bsp.h | 13 ++--- bsps/powerpc/ss555/start/irq_asm.S | 2 +- bsps/powerpc/ss555/start/vectors.S | 1 + cpukit/score/cpu/powerpc/i

[PATCH 1/2] bsps/powerpc: Hack to fix the build

The ppc405 define must be checked before the ppc403 define. The ppc405 define is provided by . The ppc403 define is provided by GCC as a built-in define if no ppc* or mpc* define is set via the command line (see GCC sources "gcc/config/rs6000/rtems.h"). Update #3425. --- bsps/powerpc/include/rt

Re: RISC-V tool chain

On 07/06/18 08:25, Sebastian Huber wrote: On 06/06/18 09:34, Chris Johns wrote: We could use an unofficial mirror on Github, e.g. https://codeload.github.com/bminor/binutils-gdb/tar.gz/c61b06a19a34baab66e3809c7b41b0c31009ed9f My main concern with using all these different download source