From: Chris Johns
---
rtemstoolkit/check.py | 36
rtemstoolkit/config.py| 60 +++--
rtemstoolkit/configuration.py | 35 ++--
rtemstoolkit/darwin.py| 13 ++-
rtemstoolkit/execute.py | 16 ++--
rtemstoolkit/freebsd.py | 14 ++--
rtemst
Hello Chris,
On 05/10/2018 06:24, chr...@rtems.org wrote:
-#
-# Support to handle use in a package and as a unit test.
-# If there is a better way to let us know.
-#
-try:
-from . import error
-from . import execute
-from . import log
-from . import options
-from . import pat
Update #3533.
---
testsuites/libtests/block02/init.c | 2 +-
testsuites/libtests/block03/init.c | 2 +-
testsuites/libtests/block06/init.c | 6 ++---
testsuites/libtests/block07/init.c | 6 ++---
testsuites/libtests/block08/bdbuf_
On 05/10/2018 15:19, Sebastian Huber wrote:
> Hello Chris,
>
> On 05/10/2018 06:24, chr...@rtems.org wrote:
>> -#
>> -# Support to handle use in a package and as a unit test.
>> -# If there is a better way to let us know.
>> -#
>> -try:
>> - from . import error
>> - from . import execute
>>
On 05/10/2018 07:49, Chris Johns wrote:
On 05/10/2018 15:19, Sebastian Huber wrote:
Hello Chris,
On 05/10/2018 06:24,chr...@rtems.org wrote:
-#
-# Support to handle use in a package and as a unit test.
-# If there is a better way to let us know.
-#
-try:
- from . import error
- from . i
On 05/10/2018 16:07, Sebastian Huber wrote:
>
> Problems appear later (this is expected):
>
> $ ./rtems-test --version
> Traceback (most recent call last):
> File "./rtems-test", line 39, in
> import rt.test
> ...
> File "/c/msys2/home/test/share/rtems/tester/rt/tftpy/TftpStates.py", lin
In standard C pointer operands are not allowed in integer constant
expression. Avoid a static assertion based on an array typedef since
this could lead to warnings ("variably modified 'x' at file scope" and
"typedef 'x' locally defined but not used");
This implementation requires unique messages.
On 05/10/2018 08:28, Chris Johns wrote:
On 05/10/2018 16:07, Sebastian Huber wrote:
Problems appear later (this is expected):
$ ./rtems-test --version
Traceback (most recent call last):
File "./rtems-test", line 39, in
import rt.test
...
File "/c/msys2/home/test/share/rtems/tester
Clang do not support -mfix-gr712rc, -mfix-ut700 and -mfix-ut699.
Therefore we adjust the CPU_CFLAGS to remove these when compiling with
Clang. Instead use
GR712RC: -mcpu=gr712rc
GR740:-mcpu=gr740
UT699/UT700: Not currently supported by clang, use LEON3 BSP.
---
bsps/sparc/leon3
From: Jacob Hansen
This commits bypasses a static assert when using the Clang compiler.
This is done as the static assertion does not compile with Clang
("static_assert expression is not an integral constant expression").
I am not sure this static assertion makes sense at all. SEM_FAILED
is used
From: Javier Jalle
---
bsps/sparc/headers.am|1 +
bsps/sparc/include/bsp/spwtdp.h | 320 ++
bsps/sparc/include/drvmgr/ambapp_bus.h |1 +
bsps/sparc/shared/spw/spwtdp.c | 1022 ++
c/src/lib/libbsp/sparc/leon2/Ma
This fixes the following test failures on LEON3 UP/SMP when
built using clang compiler:
* fsjffs2gc01
* jffs2_fserror
* jffs2_fspermission
* jffs2_fsrdwr
* jffs2_fstime
---
cpukit/libfs/src/jffs2/src/nodelist.c | 2 +-
cpukit/libfs/src/jffs2/src/readinode.c | 4 ++--
2 files changed, 3 inser
rtems-syms assumes that the compiler used is GCC. This breaks the build
if using a different compiler (such as Clang). Using the --cc argument
for rtems-syms we can specify the compiler.
A better implementation would mabe be to configure the default compiler
to LLVM when building rtems-tools?
---
malloc04 and malloctest tests from the rtems test-suite fails
when checking the return value of malloc(). The check is
optimized away and always fails.
---
testsuites/libtests/malloc04/init.c | 2 +-
testsuites/libtests/malloctest/init.c | 10 +-
2 files changed, 6 insertions(+), 6 dele
14 matches
Mail list logo