[Bug 1000637] New: tm_basic's runtime limits calculation

[bugzilla-daemon at ecoscentric dot com]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000637

           Summary: tm_basic's runtime limits calculation
           Product: eCos
           Version: CVS
          Platform: Other (please specify)
        OS/Version: Other
            Status: UNCONFIRMED
          Severity: normal
          Priority: normal
         Component: Test farm
        AssignedTo: jld@ecoscentric.com
        ReportedBy: sergei.gavrikov@gmail.com
         QAContact: ecos-bugs@ecos.sourceware.org
             Class: ---


Note: you won't meet a problem if your target allows to run upon 64 threads
together (i.e. it has enough RAM for that).

After the latest CVS checkout 2008/11/18 I found that tm_basic test does not
work anymore on my target. If I could understand the latest fix of max() macro
(done a few days ago) did reverse all checks for test limits: ntest_treads,
nmboxes, nalarms, etc. In a fact, the previous mistaken max() definition
shadows this issue.

looking at all results for eCos Real-Time characterization
http://ecos.sourceware.org/docs-latest/user-guide/real-time-characterization.html

It is not hard to notice what there weren't conditions when more than 64 treads
were running together there. So, I could assume that tm_basic's ntest_threads
limit (and same others) is defined as:

nthings = min(N, nthings); // no more than N

Unfortunately there are nthings = max(N, nthings) definitions. It was a
happiness that old max() macro in the past was defined in a fact as a 'min'
macro.

Well, it's too long to write. Just see the patch.

Regards

Sergei


-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.