about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc/messages.ftl
AgeCommit message (Collapse)AuthorLines
2025-07-26Implement support for explicit tail calls in the MIR block builders and the ↵Joel Wejdenstål-0/+2
LLVM codegen backend.
2025-07-21Move LTO symbol export calculation from backends to cg_ssabjorn3-8/+0
2025-06-19move -Ctarget-feature handling into shared codeRalf Jung-16/+0
2025-06-09-Zretpoline and -Zretpoline-external-thunk flags (target modifiers) to ↵Andrew Zhogin-7/+0
enable retpoline-related target features
2025-06-07store `target.min_global_align` as an `Align`Folkert de Vries-3/+0
2025-01-24Merge commit '9f33f846ddc06afd7ffd839ee4f18babac3f3204'Guillaume Gomez-3/+0
2024-12-11generalize 'forbidden feature' concept so that even (un)stable feature can ↵Ralf Jung-1/+1
be invalid to toggle Also rename some things for extra clarity
2024-11-04mark some target features as 'forbidden' so they cannot be (un)setRalf Jung-2/+9
For now, this is just a warning, but should become a hard error in the future
2024-09-24codegen_ssa: consolidate tied feature checkingDavid Wood-3/+0
`rustc_codegen_llvm` and `rustc_codegen_gcc` duplicated logic for checking if tied target features were partially enabled. This commit consolidates these checks into `rustc_codegen_ssa` in the `codegen_fn_attrs` query, which also is run pre-monomorphisation for each function, which ensures that this check is run for unused functions, as would be expected.
2024-03-05Merge commit 'b385428e3ddf330805241e7758e773f933357c4b' into ↵Guillaume Gomez-2/+0
subtree-update_cg_gcc_2024-03-05
2023-10-09Merge commit '11a0cceab966e5ff1058ddbcab5977e8a1d6d290' into ↵Antoni Boucher-0/+30
subtree-update_cg_gcc_2023-10-09
2023-07-20UPDATE - replace expected_simd error with one from codegen_ssaJhonny Bill Mena-3/+0
Here I am assuming we want to treat these parameters (input, first, second, third, return) as translatable
2023-07-19UPDATE - replace gcc monomorphization errors with ssa onesJhonny Bill Mena-54/+0
Reduces error duplication and makes it more consistent across backends
2023-05-25Ensure Fluent messages are in alphabetical orderclubby789-33/+33
2023-03-11Simplify message pathsest31-0/+68
This makes it easier to open the messages file while developing on features. The commit was the result of automatted changes: for p in compiler/rustc_*; do mv $p/locales/en-US.ftl $p/messages.ftl; rmdir $p/locales; done for p in compiler/rustc_*; do sed -i "s#\.\./locales/en-US.ftl#../messages.ftl#" $p/src/lib.rs; done