aboutsummaryrefslogtreecommitdiff
path: root/libjava/javax/swing/Spring$3.h
diff options
context:
space:
mode:
authorRichard Sandiford <richard.sandiford@arm.com>2025-04-07 08:03:47 +0100
committerRichard Sandiford <richard.sandiford@arm.com>2025-04-07 08:03:47 +0100
commit30a4eedfdbfeb1caaadd43738cbb0b49d7fa120b (patch)
tree0ded28a83d770f13e76dc339f5e68cac29a25d81 /libjava/javax/swing/Spring$3.h
parent4d7a634f6d41029811cdcbd5f7282b5b07890094 (diff)
downloadgcc-30a4eedfdbfeb1caaadd43738cbb0b49d7fa120b.zip
gcc-30a4eedfdbfeb1caaadd43738cbb0b49d7fa120b.tar.gz
gcc-30a4eedfdbfeb1caaadd43738cbb0b49d7fa120b.tar.bz2
combine: Avoid split_i2i3 search if i2 is unchanged [PR116398]
When combining a single-set i2 into a multi-set i3, combine first tries to match the new multi-set in-place. If that fails, combine considers splitting the multi-set so that one set goes in i2 and the other set stays in i3. That moves a destination from i3 to i2 and so combine needs to update any associated log link for that destination to point to i2 rather than i3. However, that kind of split can also occur for 2->2 combinations. For a 2-instruction combination in which i2 doesn't die in i3, combine tries a 2->1 combination by turning i3 into a parallel of the original i2 and the combined i3. If that fails, combine will split the parallel as above, so that the first set goes in i2 and the second set goes in i3. But that can often leave i2 unchanged, meaning that no destinations have moved and so no search is necessary. gcc/ PR testsuite/116398 * combine.cc (try_combine): Shortcut the split_i2i3 handling if i2 is unchanged.
Diffstat (limited to 'libjava/javax/swing/Spring$3.h')
0 files changed, 0 insertions, 0 deletions