Scope of ACVC validation

Scope of ACVC validation

[Peter Klein]

Sorry for putting the same question out again, but I ran into problems
with my Internet feed before I could collect replies.

I'd be interested in getting some expert's opinion on ACVC validation
scope:

If a compiler vendor gets validation for a 680x0 cross compilation system
with a Run Time Executive for a specific VME board, what does this mean
for a different target system, say a multi-CPU system with an extended Run
Time Executive?

Which kind of testing on the extended Run Time Executive would one expect
to support the assumption, that the system can also be considered
validated for a different target?

I know, that validation does not specifically attack RTE function, but
certain Ada constructs (e. g. tasking, exception handling) implicitely
involve the Run Time Executive, hence ACVC validation should cover a fair
amount.

Tanks in advance for any helpful reply!

Cheers from Edinburgh, capital of Scotland,

Peter

Please reply to Peter_Klein@confusion.fido.de or in this forum.

Re: Scope of ACVC validation

[Interstate Electronics Corp]

In article <b090654f%fido.de@p83.f2.n8000.z242.fidonet.org> Peter_Klein@p83.confusion.fido.de (Peter Klein) writes:

   If a compiler vendor gets validation for a 680x0 cross compilation system
   with a Run Time Executive for a specific VME board, what does this mean
   for a different target system, say a multi-CPU system with an extended Run
   Time Executive?

Absolutely nothing.  Re-validation would be required for a different
target system. 

   Which kind of testing on the extended Run Time Executive would one expect
   to support the assumption, that the system can also be considered
   validated for a different target?

Again, re-validation would be required.  I believe this is especially
strict for run-time issues; that is, that there might be some room for
maneuver for a different host using a compiler derived from the same
code, for the same target, but different targets always require
re-validation. 



-- 
--
========================================================================
Mike Elliott              mre@emerald.ccss.com               mre@lpf.org
========================================================================