Solid Sands: Buy in India

SuperTest and SuperGuard: Qualifying the Compiler and Library Underneath Your Safety-Critical Code

Tool Confidence and New-Target Bring-Up

SuperGuard Library Safety Qualification and MC/DC Coverage for the C and C++ Standard Library

The C and C++ standard libraries are the part of a safety-critical build most teams never test, because they did not write them. SuperGuard closes that gap. Per Solid Sands, it provides a detailed breakdown of the ISO C and C++ library specifications into requirements and tests, with full requirements traceability between each requirement and the test that exercises it, and reports high structural code coverage and MC/DC for the library implementation out of the box. Solid Sands describes it as “the industry’s most rigorous safety qualification suite for C and C++ libraries”.

SuperGuard covers the C standard library, and in its C++ Core configuration adds a core set of the most-demanded C++ standard-library headers, with additional headers available on request, building up through full support for C++11, C++14, and C++17. It qualifies third-party and COTS library implementations as well as libraries a team maintains itself, runs on Windows and Linux against bare-metal targets, and produces a CSV report that links requirements, test specifications, and results, the traceability artefact an ISO 26262 or IEC 62304 assessor expects. For Indian medical-device, automotive, and avionics teams, MC/DC coverage of the standard library out of the box is the differentiator: it is the same structural-coverage evidence Razorcat TESSY produces for application code, applied to the library underneath it.

C and C++ Standard-Version Coverage: The SuperTest Conformance Matrix

SuperTest can be configured to verify a compiler against the exact version of the C or C++ standard a project or market requires. The matrix below summarises the language coverage and test scope documented by Solid Sands.

Beyond language conformance, SuperTest verifies optimization correctness, data-model-specific arithmetic, and calling conventions, the compiler internals that silently change behaviour between targets and optimization levels. That is what separates compiler validation from simply trusting a widely used toolchain.

ISO 26262 Compiler and Library Tool Qualification for Automotive Software in India

Under ISO 26262, the compiler and the standard library are software tools whose confidence must be demonstrated, not assumed. Solid Sands references ISO 26262 Part 8, Clauses 11 and 12, and the ASIL C and ASIL D levels, and notes that a pre-existing qualification route can apply up to ASIL C from library binaries, while ASIL D requires structural code coverage analysis, for which the library source code is needed. The SuperTest Qualification Suite demonstrates compiler tool confidence through hand-crafted tests, high compiler code coverage, and reference-value comparison; SuperGuard supplies the library evidence with MC/DC coverage and requirements traceability.

GSAS provides the application engineering to apply this for automotive ECU and AUTOSAR teams in Bengaluru, Hyderabad, Chennai, Pune, Mumbai, and Delhi NCR, alongside Perforce Helix QAC for the MISRA and AUTOSAR C++ static analysis the same safety case requires. GSAS supplies the tools and consulting, not a certification.

DO-178C, ED-12C and DO-330 Compiler Qualification for Avionics and Defence

For airborne software, Solid Sands cites RTCA DO-178C and the essentially identical EUROCAE ED-12C, together with DO-330 (Software Tool Qualification Considerations) and its European equivalent ED-215. Solid Sands observes that compiler qualification under these standards is so challenging that it is often skipped, leaving the most safety-critical software in the aircraft resting on an unverified translation step. SuperTest and the SuperTest Qualification Suite provide the compiler tool-confidence evidence, and SuperGuard the standard-library evidence, that a DO-178C and DO-330 verification argument needs. (For hardware programmes, DO-254 governs the airborne electronic hardware this qualified software runs on, a separate but adjacent assurance track.)

GSAS supports India’s aerospace and defence software teams across the named cities with toolchain-trust application engineering. GSAS provides qualification engineering, not a DAL credit or certification.

IEC 62304 Standard Libraries as SOUP: Medical-Device Software Qualification

Under IEC 62304, a standard C or C++ library that a manufacturer adopts rather than develops in-house is Software of Unknown Provenance (SOUP), which must be assessed and its suitability justified, alongside ISO 14971, IEC 60601-1, ISO 13485, FDA, and EU MDR expectations (all per Solid Sands). SuperGuard produces that justification: it breaks the ISO library specification into requirements and tests and reports structural code coverage and MC/DC for the library implementation, with a CSV report linking requirements, test specifications, and results. The standard library moves from “unknown provenance” to qualified evidence in the safety file.

GSAS helps medical-device software teams in Bengaluru, Hyderabad, Chennai, Pune, Mumbai, and Delhi NCR scope and justify the standard library their Class B or Class C software depends on. GSAS supplies tools and engineering support, not regulatory clearance.

IEC 61508 and EN 50128 Functional Safety: Industrial and Rail Toolchain Qualification

Solid Sands notes that functional-safety standards such as ISO 26262, IEC 61508, EN 50128, and IEC 62304 all require that compilers and libraries are qualified. For industrial functional safety (IEC 61508, the base SIL standard for process, energy, and machinery control) and railway software (EN 50128 and the newer EN 50716), the same principle holds: the compiler and standard library are tools whose correct behaviour must be established as part of the safety argument. SuperTest and SuperGuard provide that compiler-and-library tool-confidence evidence for industrial control, energy, and rail-signalling teams.

GSAS supports industrial automation, robotics, energy, and rail customers across the named Indian cities, integrating Solid Sands qualification with the static and dynamic verification their SIL or SSIL programme already runs. Robotics is one of the markets Solid Sands explicitly names for SuperTest, alongside automotive, rail, aerospace and avionics, medical, and semiconductor.

RISC-V and Custom-ISA Compiler Backend Bring-Up and Qualification

India’s semiconductor and RISC-V push needs more than silicon: a new processor needs a trustworthy compiler. The Code Generator Trainer is a bootstrapping pack of nearly one thousand test files across 25 graduated levels, from minimal integer arithmetic through register allocation, calling conventions, and variable arguments, for developing a new compiler code generator. Once a backend is bootstrapped, SuperTest drives it to full ISO conformance and SuperGuard qualifies its standard library, a path from a bare new code generator to a qualifiable toolchain.

Per the Solid Sands Toolchains and Targets resource, SuperTest’s supported targets already include RISC-V, alongside Arm, AURIX / TriCore, RH850, Power Architecture, RL78, RX, MSP430, AVR, 8051, and x86/x86-64. GSAS provides backend bring-up and qualification support for India’s custom-silicon and RISC-V teams across Bengaluru, Hyderabad, Chennai, Pune, Mumbai, and Delhi NCR.

The Complete Shift-Left Verification Stack: Static Analysis, Dynamic Test, and Toolchain Qualification

Most embedded software testing stacks in India cover two of three layers, static analysis on the source and dynamic test with code coverage, then assume the compiler and standard library beneath them are correct. Solid Sands closes that third layer, the one the others rely on:

Static analysis with Perforce Helix QAC proves your source follows the MISRA and AUTOSAR rules. Dynamic testing with Razorcat TESSY proves your source behaves correctly and reports MC/DC code coverage. Both, however, assume the compiler faithfully translates that source into object code and that the library functions you call are correct. Solid Sands qualifies exactly those assumptions, so an ISO 26262 or DO-178C team can present a single, coherent toolchain-trust story across its whole software testing toolchain, from static analysis and code coverage up through compiler and standard-library qualification.

Supported Compiler Toolchains and Targets

Per the Solid Sands Compiler Toolchains and Targets resource, SuperTest can be configured to qualify any C or C++ compiler toolchain for any execution environment. Named example configurations include GCC (all versions), Clang (all versions), IAR Embedded Workbench, Green Hills, TASKING, HighTec, Wind River Diab, Texas Instruments Code Composer Studio, Keil uVision5, Microchip MPLAB X, NXP CodeWarrior and S32 Design Studio, Renesas CS+ and e2 studio, STMicroelectronics STM32CubeIDE, Cadence Xtensa XCC, Analog Devices CrossCore, and Microsoft MSVC, across targets including Arm, AURIX / TriCore, RH850, Power Architecture, RISC-V, RL78, RX, MSP430, AVR, 8051, and x86/x86-64.

Why Buy Solid Sands SuperTest and SuperGuard from GSAS India

GSAS Micro Systems is the India engineering partner for Solid Sands. We provide SuperTest and SuperGuard licensing with INR invoicing, onboarding, and qualification consulting, and we integrate them with the static analysis and dynamic testing tools your team already runs. Our functional-safety engineers in Bengaluru, Hyderabad, Chennai, Pune, Mumbai, and Delhi NCR help automotive, aerospace and defence, medical-device, and semiconductor teams qualify their compiler and standard library against the exact ISO standard version their project targets, and assemble the tool-confidence evidence that ISO 26262, DO-178C, and IEC 62304 assessments require.

For India’s growing RISC-V and custom-silicon teams, the Code Generator Trainer and SuperTest together provide a path from a new compiler backend to a qualified, standard-conformant toolchain, so the software built on top of new hardware rests on the same solid foundation as the chip itself.