ddb0266645
## Summary Replaces the Python `propscheck.py` validation script with TypeScript code that: - Uses a testable validator module (`lib/properties-validator.ts`) - Has comprehensive unit tests (71 tests in `test/properties-validation-tests.ts`) - Integrates with the existing property loading infrastructure - Runs as part of the normal test suite ## Changes - **New validator module** (`lib/properties-validator.ts`): - Raw file validation: duplicate keys, empty list elements, typos, suspicious paths - Orphan detection: compilers, groups, formatters, tools, libraries - Cross-file duplicate compiler ID detection - Disabled allowlist support (`# Disabled: id1 id2`) - Invalid property format detection (leverages `parseProperties()` with new `collectErrors` option) - Missing compilers list detection for language files - **Property library enhancement** (`lib/properties.ts`): - Added `collectErrors` option to `parseProperties()` for structured error collection - **New npm script**: `npm run test:props` for quick property validation - Set `CHECK_LOCAL_PROPS=true` to include `.local.properties` files - **Updated references**: - CI workflow no longer calls propscheck.py - Pre-commit hook uses `npm run test:props` - CE Properties Wizard uses the new validation - **Removed**: `etc/scripts/util/propscheck.py` and `propschecktest.py` ## Test plan - [x] All 71 unit tests pass - [x] Integration tests validate real config files - [x] `npm run test:props` works standalone - [x] CE Properties Wizard validation works - [x] CI passes 🤖 Generated with [Claude Code](https://claude.ai/code) --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
How do I ?
This is a how-to guide for the user-interface presented by Compiler Explorer. This doesn't cover the details of how to set up or modify Compiler Explorer for your own needs. For that, please check the documents which already cover topics like:
- Adding a language
- Adding a compiler
- Adding a library
- Adding a tool
- and many more at compiler-explorer/docs
Fast links:
Change the assembly syntax from Intel
The option to switch assembly from Intel to AT&T syntax is present in the Output option of each compiler. If enough
space is not present, the option also presents itself as the gear symbol (⚙)
Compare the time taken by compilation and networking
This is the symbol that looks like a bar graph (📊). If your compilations are taking long, you can use this to check the time taken by:
- Networking, JavaScript, waiting for events, etc.
- Checking the cache and retrieving from it on a cache-hit
- Compilation (on force compilation or cache-miss)
- Parsing the generated assembly before presenting it
View intermediate information provided by the compilers
Though both GCC and Clang create supplementary outputs along with assembly (shown by default), and an executable (created if an executor has been added), the exact nature of the outputs and their formats differ between the compilers.
GCC allows the Tree, IPA, RTL and graph outputs, while Clang allows optimization, AST, IR and graph outputs. Some outputs (e.g. RTL or graph) also have a rich set of options in the UI to enable focussing on a particular function or compiler stage.