From: iec@netcom12.netcom.com (Interstate Electronics Corp)
Subject: Re: Scope of ACVC validation
Date: Sat, 24 Sep 1994 20:09:05 GMT
Date: 1994-09-24T20:09:05+00:00 [thread overview]
Message-ID: <IEC.94Sep24130905@netcom12.netcom.com> (raw)
In-Reply-To: Peter_Klein@p83.confusion.fido.de's message of Mon, 19 Sep 1994 22:30:00 +0200
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
========================================================================
prev parent reply other threads:[~1994-09-24 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-09-19 20:30 Scope of ACVC validation Peter Klein
1994-09-24 20:09 ` Interstate Electronics Corp [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox