tree 87f6a2b5bc0b5aae208cb394c82ff2c0020946d6
parent bf02d3b7b028850c1130ce80291d26d5a5fdc42c
author Cristian Assaiante <cristianassaiante@outlook.com> 1768994086 +0100
committer GitHub <noreply@github.com> 1768994086 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJpcLUmCRC1aQ7uu5UhlAAANKgQAJVTHXP3t7Q8ArOOpRtA97CN
 5brS6Kdop6+xtw+d6opZwfp2olE1xhzPHiP09BLATvgUYAZKxfdSALZC/T4DSCnh
 So0kKVYQ01qTgkl/Hetee4Wlf6KH4ySJ14/w8oCvgAqEJbjqyX0jqiR9HNLvygTU
 tO7JFyPbm/3Jb5LHGIXAjsP7AkPAFY/JKnevgOdPz2WTaaz9HvUFBLExvIIqQGCj
 kW5QaLEK3tjo6cNOaBIKA+PEfAuxAuY6mKRt95BTRK3Qjp2amr8ePsrN9hGx7VOn
 26YlW/QEckf5vIRhmnvNFHb1PP/oh0olDdUNA7wmrrvMD/rqhoWBw6CVg9L5x0Lw
 8aiqjDh2QOW906mBq0hLp9Bh+huaA74zIUbCj2/9Q6DoQPTPTGGNp0fI+DsczKMe
 vsfljNjzDrrCPdhk8osXAvSg4NKY7oExiku288WlDr+JVyjCCbOsYkWJx9wHENtF
 AoufV8v/F6VKkGtjZaOLS/gLWqflFtDmSOpMJwWseuNuRqf+BcK9hCwMF7TxUrlN
 gqROsFBCSrNTzeua/AexkEgN8xRSVO9irF/TU7mr3CnnAVncNmFXstLe3ttpUE4V
 pELmfi3NwCcWwI9G+OJwKsiduuC1xxPqki58ZDC4DBwHNfwCDHaSkIA3pqD3N6/1
 /c56Jnp2D1U5ZsMBfato
 =ysHU
 -----END PGP SIGNATURE-----
 

[OptBisect] Merge shouldRun logic of -opt-bisect and -opt-disable (#177122)

Hi everyone,

After the introduction of `-opt-disable` in,
one of its main limitations has been that it cannot be used together
with `-opt-bisect`, since `getGlobalPassGate()` returns either
`getOptDisabler()` or `getOptBisector()`, but not both. Allowing them to
work simultaneously would be useful for disabling individual passes
while still restricting the pipeline. This is especially relevant given
the recent updates to `-opt-bisect`, such as interval support.

For example, when a defect is caused by a particular pass but its impact
is masked by another, it can be difficult to identify the actual culprit
through bisecting alone. Being able to disable passes individually while
using `-opt-bisect` would make this process much more efficient.

In this PR, I have merged the logic of the two flags so that they can
interoperate. Specifically:

- Removed the `OptDisable` class, as its functionality has been
integrated into `OptBisect`.
- Removed the `-opt-disable-enable-verbosity` flag, since verbosity now
behaves identically to `-opt-bisect`.
- Updated all affected tests and added a new test to verify that both
flags work correctly together.

There is one potential change I am considering for clarity but have not
yet implemented. Currently, log messages continue to use the `BISECT:`
prefix. With the merged behavior, it might make sense to revise this
message to better reflect the combined functionality.