Do we actually support building v8 on both big-endian and little-endian versions of a given architecture? I'm guessing this is mostly for power or mips?

Or can we just derive this from target_cpu ?

As suggested by laforge@ and a conversation w/ the monorail folks, I'm going to try tracking V8 GN-Migration related issues by *just* using the Proj-GN-Migration-V8 label, and not using blocking/rollup bugs, so that we can use blocking for just tasks that truly need to be completed before other tasks can make progress.

This should be derivable using the cpu flags. This would go in the build configuration rather than the GN tool proper.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Is this still needed?

I'm not sure. For MIPS big endian we would need this, but I don't think we actually support that. Closing for now.