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

2018-06-10 Thread Joel Sherrill
On Mon, Jun 11, 2018, 8:14 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 11/06/18 08:10, Joel Sherrill wrote: > > > > > > On Mon, Jun 11, 2018, 7:53 AM Sebastian Huber > > > > wrote: > > > > On 08/06/18 04:19, Chris Johns wrote

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

2018-06-10 Thread Sebastian Huber
On 11/06/18 08:10, Joel Sherrill wrote: On Mon, Jun 11, 2018, 7:53 AM Sebastian Huber > wrote: On 08/06/18 04:19, Chris Johns wrote: > On 07/06/2018 16:11, Sebastian Huber wrote: >> On 07/06/18 07:53, Chris Johns wrote: >>> On 07/06/

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

2018-06-10 Thread Joel Sherrill
On Mon, Jun 11, 2018, 7:53 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 08/06/18 04:19, Chris Johns wrote: > > 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

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

2018-06-10 Thread Sebastian Huber
On 08/06/18 04:19, Chris Johns wrote: 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/s

Re: RISC-V tool chain

2018-06-10 Thread Sebastian Huber
On 08/06/18 07:54, Chris Johns wrote: 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

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

2018-06-10 Thread Amaan Cheval
On Sun, Jun 10, 2018 at 12:38 AM Joel Sherrill wrote: > > > > On Fri, Jun 8, 2018 at 7:45 PM, Chris Johns wrote: >> >> On 9/6/18 10:00 am, Joel Sherrill wrote: >> > On Thu, Jun 7, 2018, 9:01 PM Chris Johns > > > wrote: >> > > and what >> > > discussions we need to

Re: error while building leon3 with gcov flags

2018-06-10 Thread Vijay Kumar Banerjee
On Sun, 10 Jun 2018, 20:52 Joel Sherrill, wrote: > > > On Sat, Jun 9, 2018, 6:02 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 10 June 2018 at 04:16, Joel Sherrill wrote: >> >>> I suggest this because it is a work around for you. The long term >>> solution could be to add

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

2018-06-10 Thread Amaan Cheval
On Sat, Jun 9, 2018 at 5:26 AM Chris Johns wrote: > > On 9/6/18 2:39 am, Amaan Cheval wrote: > > On Fri, Jun 8, 2018 at 7:31 AM, Chris Johns wrote: > >> 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

Re: error while building leon3 with gcov flags

2018-06-10 Thread Joel Sherrill
On Sat, Jun 9, 2018, 6:02 PM Vijay Kumar Banerjee wrote: > On 10 June 2018 at 04:16, Joel Sherrill wrote: > >> I suggest this because it is a work around for you. The long term >> solution could be to add the symbol to newlib's dummy RTEMS crt0.c, add it >> to librtemscpu.a (which is the tempora

Re: [PATCH v2 2/2] Adding trace documentation

2018-06-10 Thread Vidushi Vashishth
>The formatting is the Emacs default for ReST. It would be nice to maintain that format. Oh yes I will fix that. On Sun, Jun 10, 2018 at 5:56 PM, Chris Johns wrote: > > > On 10 Jun 2018, at 8:32 pm, Gedare Bloom wrote: > > > > I can't give a detailed review, but one possible problem I notice

Re: [PATCH v2 2/2] Adding trace documentation

2018-06-10 Thread Chris Johns
> On 10 Jun 2018, at 8:32 pm, Gedare Bloom wrote: > > I can't give a detailed review, but one possible problem I notice is > the line lengths. I think in the docs we also have 79/80 character > widths for lines. Please set your editor to hard-wrap at 79 or 80, and > break the long lines. (Unles

Re: [PATCH v2 2/2] Adding trace documentation

2018-06-10 Thread Gedare Bloom
I can't give a detailed review, but one possible problem I notice is the line lengths. I think in the docs we also have 79/80 character widths for lines. Please set your editor to hard-wrap at 79 or 80, and break the long lines. (Unless I'm mistaken about the line length in the doc files.) On Sun,