| Auto-Submit | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
#if BUILDFLAG(SUPPORTS_CODE_ORDERING)Just wondering if lack of code ordering support actually implies no support for unwinding? Or is it being used as a proxy for something else?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
Not too familiar with all the unwinding edge cases. I believe we don't require unwinding support in component builds (we mainly care about this working in release builds) -- so this is likely fine?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
Eric Seckler\+cc @esec...@chromium.org, since you might know the code a bit more :)
Not too familiar with all the unwinding edge cases. I believe we don't require unwinding support in component builds (we mainly care about this working in release builds) -- so this is likely fine?
Makes sense, I am not too sure either whether it currently works in component builds or not.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
#if BUILDFLAG(SUPPORTS_CODE_ORDERING)Just wondering if lack of code ordering support actually implies no support for unwinding? Or is it being used as a proxy for something else?
Looking at what depends on code ordering, it's just `is_chrome_module()` part. I don't think the unwinding depends on it.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Android: disable enable_code_ordering=false for is_component_build=false
It doesn't make sense for component builds.
My actual motivation is that I'd like to explore using mold/wild for
debug Android builds, and they don't support the associated linker
script.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |