diff options
| author | Richard Sandiford <richard.sandiford@arm.com> | 2024-06-18 12:22:30 +0100 |
|---|---|---|
| committer | Richard Sandiford <richard.sandiford@arm.com> | 2024-06-18 12:22:30 +0100 |
| commit | 01044471ea39f9be4803c583ef2a946abc657f99 (patch) | |
| tree | b2c5bb1b42b78b8ee974a106929e8a8adbc4a86a /gcc/expr.cc | |
| parent | c9b96a68860bfdee49d40b4a844af7c5ef69cd12 (diff) | |
| download | gcc-01044471ea39f9be4803c583ef2a946abc657f99.zip gcc-01044471ea39f9be4803c583ef2a946abc657f99.tar.gz gcc-01044471ea39f9be4803c583ef2a946abc657f99.tar.bz2 | |
Make force_subreg emit nothing on failure
While adding more uses of force_subreg, I realised that it should
be more careful to emit no instructions on failure. This kind of
failure should be very rare, so I don't think it's a case worth
optimising for.
gcc/
* explow.cc (force_subreg): Emit no instructions on failure.
Diffstat (limited to 'gcc/expr.cc')
0 files changed, 0 insertions, 0 deletions