This is the test committed with the original ticket #2124 ticket see
https://devel.rtems.org/ticket/2124 and
http://comments.gmane.org/gmane.os.rtems.devel/78. The test is a bit
confusing because the output in .scn matches when configured without
RTEMS_ENABLE_STRICT_ORDER_MUTEX=1 but doesn't match
Is this error with the default gglg priority inherit algorithm or with the onf
which restores at each unlock step? If the default algorithm, the test is
broken. If the alternative algorithm, the test needs to be reworked a bit to
check the correct behavior for each algorithm.
Fwiw the test shou
Hi,
I tried to run spsem02 test case and found that the results were not as per
mentioned in the respective document. And even document had some typos
which I have corrected in my branch.
*** BEGIN OF TEST SPSEM 2 ***
init: S0 created
init: S1 created
init: TA01 created with priority 36
init: TA02
Hi,
installing pax work. But you have to again do the bootstrap step,
configuration and compiling.
Thanks.
Thanks,
Saurabh Gadia
On Fri, Jun 5, 2015 at 12:44 PM, Gedare Bloom wrote:
> I'm not really sure, but I think you probably have to re-run configure.
>
> On Fri, Jun 5, 2015 at 3:40 PM, Sa
Ok. Thanks a lot. Will continue with compiling and JPF setup this week as
discussed with Cyrille. And if time permits will look into how to emulate
the things in JPF. And also provide ppt in deoxygen for revised rtems code.
On Friday, June 5, 2015, Gedare Bloom wrote:
> Hi Saurabh,
>
> This is a
Hi Saurabh,
This is a current problem in RTEMS. You need to have 'pax' installed
on your development host to build the dl tests. So, it looks good to
me!
Gedare
On Thu, Jun 4, 2015 at 9:16 PM, Saurabh Gadia wrote:
> I am sorry for not attaching the patch and configuration command:
>
> ../rtems/
I am sorry for not attaching the patch and configuration command:
../rtems/configure --target=sparc-rtems4.11 --enable-rtemsbsp=sis
--enable-tests --disable-posix ENABLE_STRICT_ORDER_MUTEX=1
Thanks,
Saurabh Gadia
On Thu, Jun 4, 2015 at 6:08 PM, Saurabh Gadia wrote:
> Hi,
> I worked out that
Hi,
I worked out that bug related to strict_mutex and gone past that bug. But
now I have issue while compiling the libtests. Below is the error log:
'''
sparc-rtems4.11-size syscall01.exe
text databssdechexfilename
266128 6064 11456 283648
Hi Saurabh,
Please try to figure out how to fix the compile-error. You can see
that the problem occurs in the #ifdef'd STRICT_ORDER_MUTEX_CODE, so
that makes sense why others have not observed the same issue. It
appears you will have to reconcile the new _Thread_Change_priority
arguments with what
I wanted to test the ENABLE_STRICT_ORDER_MUTEX=1 related sptests for
"nested mutex" GSOC project. So please let me know what can be done.
Thanks,
Saurabh Gadia
On Sun, May 31, 2015 at 9:33 PM, Saurabh Gadia wrote:
> Hi,
> so I am working for sparc-sis setting and master branch. And if you see
Hi,
so I am working for sparc-sis setting and master branch. And if you see the
code in threadimpl.h and threadchangepriority.c and coremutexsurrender.c
the definition of *_Thread_Change_priority() *is having mismatch calling.
Git records says that there was change to above function structure done
Does re-running bootstrap in the source dir and re-configuring sort it?
--
Nick Withers
Embedded Systems Programmer
Department of Nuclear Physics, Research School of Physics and Engineering
The Australian National University (CRICOS: 00120C)
On Sun, 2015-05-31 at 20:31 -0400, Joel Sherrill wrote
On 05/31/2015 07:57 PM, Saurabh Gadia wrote:
The problem is on master branch
Just a suggestion that you might need to run ./bootstrap from rtems root
after a "git pull" that adds or removes files. I had a similar problem
but with a different file.
-gene
___
More information is needed. Target architecture, bsp, configure command.
I have been building all bsps regularly and unless it got broken this weekend,
something else is up
On May 31, 2015 7:57:04 PM EDT, Saurabh Gadia wrote:
>The problem is on master branch
>
>
>Thanks,
>
>
>Saurabh Gadia
>
>
The problem is on master branch
Thanks,
Saurabh Gadia
On Sun, May 31, 2015 at 4:44 PM, Saurabh Gadia wrote:
> Logs:
>
> make[6]: Entering directory
> `/home/saurabh/dev1/kernel/b-sis/sparc-rtems4.11/c/sis/cpukit/score'
> make[6]: *** No rule to make target `src/apimutexislocked.c', needed by
Logs:
make[6]: Entering directory
`/home/saurabh/dev1/kernel/b-sis/sparc-rtems4.11/c/sis/cpukit/score'
make[6]: *** No rule to make target `src/apimutexislocked.c', needed by
`src/libscore_a-apimutexislocked.o'. Stop.
make[6]: Leaving directory
`/home/saurabh/dev1/kernel/b-sis/sparc-rtems4.11/c/s
16 matches
Mail list logo
