1. Qualification scope¶

This qualification applies to Ferrocene rolling, limited to:

rustc 1.84.0, limited to the Rust language as described in the Ferrocene Language Specification, and according to the requirements and restrictions outlined in this safety manual.

This qualification is restricted to the following environment:

Host	Target	Uncertified Libraries
x86-64 Linux (glibc)	Armv8-A bare-metal	`core`, `alloc`
x86-64 Linux (glibc)	x86-64 Linux (glibc)	`core`, `alloc`, `std`, `proc_macro`, `test`
x86-64 Linux (glibc)	x86-64 QNX® Neutrino® 7.1.0	`core`, `alloc`, `std`, `proc_macro`, `test`
x86-64 Linux (glibc)	Armv8-A QNX® Neutrino® 7.1.0	`core`, `alloc`, `std`, `proc_macro`, `test`

The libraries provided are evaluated and tested within the scope of Ferrocene qualification for compiler use only. The use of these libraries by end-use code is outside the scope of the current Ferrocene qualification. It is the end-user responsibility to certify these libraries if they are used in their code.

1.1. User responsibility¶

According to clause 11.4.2 of [ISO-26262:2018] part 8, the user shall verify the validity of the predetermined TCL prior to the use of this software tool in a safety-related development.

Furthermore, according to clause 11.4.3 of [ISO-26262:2018] part 8, the user shall ensure the usage, the environment, and the functional constraints of this software tool comply with its evaluation criteria or its qualification.

Additionally, according to [IEC 62304:2006 + AMD 1:2015], a manufacturer of medical device software shall consider the used tools in the software development plan (clause 5.1.4) and in their configuration item control (clauses 5.1.10 and 5.1.11). Although [IEC 62304:2006 + AMD 1:2015] does not come with its own scheme of tool classification and validation, it recommends in Annex C.7 the usage of techniques, tools and methods as defined in [IEC-61508:2010].

Ferrocene is accompanied by the appropriate documentation to support this process.