On Tue, Mar 29, 2022 at 2:59 PM Kamlesh Bharodiya
wrote:
> Hi Joel,
>
> I had tried to run the program using integrated simulator with gdb. That
> didn't work for me (need to figure out).
>
Hmm.. sis as integrated with gdb was disabled in favor of the more powerful
standalone newer versions of s
Make the task configuration reusable.
Update #3716.
---
.../testsuites/validation/libvalidation.yml | 1 +
testsuites/validation/tc-barrier-ident.c | 5 +-
testsuites/validation/tc-message-ident.c | 5 +-
testsuites/validation/tc-part-ident.c | 5 +-
testsuites/validation/
---
cpukit/include/rtems/rtems/tasks.h| 6 +-
.../validation/validation-smp-only-0.yml | 1 +
testsuites/validation/tc-task-smp.c | 146 ++
testsuites/validation/tc-task.c | 54 ++-
testsuites/validation/tx-support.c|
Hi Dr. Joel,
I just sent an update which addresses these issues.
Thanks!
Sincerely,
Matt
On 28.03.22 23:13, Joel Sherrill wrote:
I don't see anything obviously wrong but I don't have any idea what
the test is actually trying to exercise.
How about some comments and is there a doc file in t
From: Matt Joyce
Added tests for exit procedures to ensure proper resource
cleanup. The test now checks cleanup for files assigned
to stdio streams and non-stdio streams.
---
testsuites/libtests/newlib01/init.c | 120 +-
testsuites/libtests/newlib01/newlib01.doc | 5 +
From: Matt Joyce
Version 3 adds comments for clarification and updates the doc file.
Matt Joyce (1):
newlib01: Added tests for exit procedures
testsuites/libtests/newlib01/init.c | 120 +-
testsuites/libtests/newlib01/newlib01.doc | 5 +-
2 files changed, 101 inse
---
c-user/task/directives.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/c-user/task/directives.rst b/c-user/task/directives.rst
index ce2013c..708286f 100644
--- a/c-user/task/directives.rst
+++ b/c-user/task/directives.rst
@@ -86,9 +86,9 @@ identifier is returned
On 26/03/2022 23:48, Joel Sherrill wrote:
The Software Engineering Guide example uses "Copyright" but a lot of places
in the code base use "COPYRIGHT". This is sometimes followed by (c) rather
than the (C) indicated in the guide.
The format in the Software Engineering Manual follows the GNU cod