---
rtems/config/tools/rtems-gcc-6.3.0-newlib-2.5.0.20170323-1.cfg | 8
1 file changed, 8 insertions(+)
diff --git a/rtems/config/tools/rtems-gcc-6.3.0-newlib-2.5.0.20170323-1.cfg
b/rtems/config/tools/rtems-gcc-6.3.0-newlib-2.5.0.20170323-1.cfg
index fd4703c..c865910 100644
--- a/rtems/
---
rtems/config/tools/rtems-gdb-7.12-1.cfg | 2 ++
1 file changed, 2 insertions(+)
diff --git a/rtems/config/tools/rtems-gdb-7.12-1.cfg
b/rtems/config/tools/rtems-gdb-7.12-1.cfg
index 52c9fa2..b8b7e91 100644
--- a/rtems/config/tools/rtems-gdb-7.12-1.cfg
+++ b/rtems/config/tools/rtems-gdb-7.12-1
On 18/05/17 01:08, Pham, Phong wrote:
Hi Developers,
Currently:
…\rtems\cpukit\sapi\include\rtems\fatal.h
is implemented as
RTEMS_NO_RETURN RTEMS_INLINE_ROUTINE void rtems_fatal(
rtems_fatal_source fatal_source,
rtems_fatal_code error_code
)
{
_Terminate( fatal_source, error
Hi Developers,
Currently:
...\rtems\cpukit\sapi\include\rtems\fatal.h
is implemented as
RTEMS_NO_RETURN RTEMS_INLINE_ROUTINE void rtems_fatal(
rtems_fatal_source fatal_source,
rtems_fatal_code error_code
)
{
_Terminate( fatal_source, error_code );
}
I suggest to move the implementation
On 17/05/17 13:39, Kirspel, Kevin wrote:
I got a message that the patch was too large and held for review. Is there a
process for someone to review large patches and release them? If not, I can
send you the patch directly.
You can send me v2 directly.
--
Sebastian Huber, embedded brains Gm
OK. I will just stick with approach 1.
Kevin Kirspel
Electrical Engineer - Sr. Staff
Idexx Roswell
235 Hembree Park Drive
Roswell GA 30076
Tel: (770)-510- ext. 81642
Direct: (770)-688-1642
Fax: (770)-510-4445
-Original Message-
From: devel [mailto:devel-boun...@rtems.org] On Behalf O
I got a message that the patch was too large and held for review. Is there a
process for someone to review large patches and release them? If not, I can
send you the patch directly.
Kevin Kirspel
Electrical Engineer - Sr. Staff
Idexx Roswell
235 Hembree Park Drive
Roswell GA 30076
Tel: (770)-5