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 9.2.0 and those that
cannot have specific versions?
Only Powe
On 14/8/19 3:02 pm, Sebastian Huber wrote:
> On 14/08/2019 01:52, Chris Johns wrote:
>> On 13/8/19 3:02 pm, Sebastian Huber wrote:
>>
>>> the patch just changed GCC 9.1 to 9.2 on all targets which use GCC 9, these
>>> are
>>> or1k, riscv, and x86_64.
>>
>> The change as broken MacOS due to this bu
Hello,
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
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189
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 rtems-tools repo has strong support for C++ and it brings a
ra
On 14/08/2019 01:52, Chris Johns wrote:
On 13/8/19 3:02 pm, Sebastian Huber wrote:
the patch just changed GCC 9.1 to 9.2 on all targets which use GCC 9, these are
or1k, riscv, and x86_64.
The change as broken MacOS due to this bug ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
I p
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 rtems-tools repo has strong support for C++ and it brings a
range of benefits, for example no need to c
Hello Chris,
>
> sorry for the rush, but what do you think of this patch? I would like to
> integrate the tracing work of the GSoC project and this patch is a
> blocking point.
>
Please review the patches. This need to be integrated in master branch
before 19th August (GSoC ends). I have to prepar
On 14/8/19 8:34 am, Joel Sherrill wrote:
> Since I don't know how to attach gdb to the new sis for griscv, I emailed Jiri
> privately.
Does `-gdb` ...
https://git.rtems.org/sis/tree/sis.c#n133
... work?
Chris
___
devel mailing list
devel@rtems.org
htt
On 13/8/19 3:02 pm, Sebastian Huber wrote:
> the patch just changed GCC 9.1 to 9.2 on all targets which use GCC 9, these
> are
> or1k, riscv, and x86_64.
The change as broken MacOS due to this bug ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
I posted build results showing the error i
On Wed, Aug 14, 2019 at 4:04 AM Joel Sherrill wrote:
>
>
> On Tue, Aug 13, 2019 at 5:09 PM Vaibhav Gupta
> wrote:
>
>>
>>
>> On Mon, Aug 12, 2019 at 11:50 PM Joel Sherrill wrote:
>>
>>> Can you post or email me privately the full patch? I can try to see what
>>> I spot.
>>>
>> I have sent you t
On Tue, Aug 13, 2019 at 5:09 PM Vaibhav Gupta
wrote:
>
>
> On Mon, Aug 12, 2019 at 11:50 PM Joel Sherrill wrote:
>
>> Can you post or email me privately the full patch? I can try to see what
>> I spot.
>>
> I have sent you the patch.
>
>>
>> Can you check with objdump or gdb that the methods whi
On Mon, Aug 12, 2019 at 11:50 PM Joel Sherrill wrote:
> Can you post or email me privately the full patch? I can try to see what I
> spot.
>
I have sent you the patch.
>
> Can you check with objdump or gdb that the methods which don't appear to
> work
> are actually the RISC-V implementation? Lo
Ok that seems good to me.
On Tue, Aug 13, 2019, 11:30 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> - Am 13. Aug 2019 um 19:05 schrieb Gedare Bloom ged...@gwmail.gwu.edu:
>
> > If you can make different rules for HTML than PDF, the Chapter part could
> > be omitted in HTML
- Am 13. Aug 2019 um 19:05 schrieb Gedare Bloom ged...@gwmail.gwu.edu:
> If you can make different rules for HTML than PDF, the Chapter part could
> be omitted in HTML since one will expect the link to work. PDF should be
> usable even without links.
>
> I'd change it to use for example "Chap
Hi,
Last time we discussed about the PRU-Shell command, we decided it should be
realised as a libBSD shell command.
The reason was the driver being located in libBSD.
I tried developing the command in my App first.
But this would be more work, than just directly developing in libBSD.
So my quest
On 13/08/2019 11:12, Christian Mauderer wrote:
Thanks for the patch. For everyone who didn't follow the previous
discussion: Gedare suggested that the copyright should be added here:
https://lists.rtems.org/pipermail/devel/2019-August/027204.html
Do we have a specific order in the copyright? Cur
Thanks for the patch. For everyone who didn't follow the previous
discussion: Gedare suggested that the copyright should be added here:
https://lists.rtems.org/pipermail/devel/2019-August/027204.html
Do we have a specific order in the copyright? Currently it seems to be
newest first.
Best regards
---
user/index.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/user/index.rst b/user/index.rst
index eff85f3..0e644c9 100644
--- a/user/index.rst
+++ b/user/index.rst
@@ -10,6 +10,7 @@ RTEMS User Manual (|version|).
.. topic:: Copyrights and License
+| |copy| 2019 Vijay Kumar Bane
18 matches
Mail list logo
