tree 6384d910dd65482cd28bcad3d9fd7dae9496f0d0
parent 1237f4b8efaf2503749d760825ec16a64cd25364
author tjgq <tjgq@google.com> 1766093530 -0800
committer Carmen Chui <carmenchui@google.com> 1768146064 -0800
gpgsig -----BEGIN SSH SIGNATURE-----
 U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgKGv7sLM+pEIDOAfTydgJW53atR
 dADtO6XLKIRKDwcvIAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
 AAAAQJQgyDkckWsDgJn3H/SdGDWYFf1y4c72G4qMyYg7ljJ69T4WaFVYrZNsrW6tOIvEu+
 tD9gvOnkjIbfpGHJJfxQg=
 -----END SSH SIGNATURE-----

Automated rollback of commit cb9bd8615210dda2104f79d281938e47187dc2de.

*** Reason for rollback ***

Causes a Blaze performance regression .

*** Original change description ***

Add support for multiple module interfaces per `cc_library`

When multiple `module_interfaces` are specified on a single `cc_library`, the individual compilation actions form a DAG based on `import`s between these modules. Consider the following situation:

* `a.cppm` imports `b.cppm`, both of which are in the `module_interfaces` of a single `cc_library`.
* Building the target populates the action cache with an entry for `a.pcm` that store...

***

PiperOrigin-RevId: 846394946
Change-Id: Ia2d5d8a6dd28186db7f1b61f950fbe0565810ea7