What ICC are you referring to?

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 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

Do you have more details about this? Is there any build-specific code in gyp files regarding this?

I didn't find any icc/icl specific code in V8's gyp configurations. So I assume this is only about setting CC/CXX? This wouldn't be anything specific to V8 and could be supported by adding a new toolchain config to either Chromium's or V8's GN configs.

Right now, it is unclear to me who the stakeholders of this are. So I'd like to outsource support for this. If this is needed, I'll support reviewing a CL that introduces the required configurations, but I'm a bit reluctant in pushing it.

We could also close this as wontfix for now as it is not officially supported and isn't on the critical path of deprecating gyp in V8.

I think we can just WontFix this. It's not hard to add if someone wants to add it back in at some point.