| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-05-19 | in aarch64 asm parse error tests, only test cases specific to that target | Folkert de Vries | -106/+1 | |
| this is more in line with the x86 parse error tests. The cross-platform tests were more complete anyway | ||||
| 2025-05-18 | delay error for unsupported options | Folkert de Vries | -2/+0 | |
| 2024-08-13 | stabilize `asm_const` | Folkert | -2/+0 | |
| 2024-07-27 | update aarch64 asm tests | Folkert | -0/+2 | |
| 2024-02-16 | [AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives | 许杰友 Jieyou Xu (Joe) | -1/+1 | |
| 2023-01-27 | Relax ordering rules for `asm!` operands | Amanieu d'Antras | -15/+8 | |
| The `asm!` and `global_asm!` macros require their operands to appear strictly in the following order: - Template strings - Positional operands - Named operands - Explicit register operands - `clobber_abi` - `options` This is overly strict and can be inconvienent when building complex `asm!` statements with macros. This PR relaxes the ordering requirements as follows: - Template strings must still come before all other operands. - Positional operands must still come before named and explicit register operands. - Named and explicit register operands can be freely mixed. - `options` and `clobber_abi` can appear in any position. | ||||
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -0/+133 | |
