Fix iar exporter - flags duplication and consolidations

[0xc0170]

We need to distinguish between cmd flags and exporters flags, they are not the same.

cc @theotherjimmy

[theotherjimmy]

I don't like that we have to remove the cpu from the common flags specifically in the exporter, but I understand the reasoning.

[theotherjimmy]

👍

[sg-]

If you make a change to IAR we MUST run tests against IAR. This is a breaking change.

[0xc0170]

If you make a change to IAR we MUST run tests against IAR. This is a breaking change.

The only breaking change in here could be VLA, and that dlib config? I run local tests, did not spot any regession, I'll rebase this fix, and rerun the bot

This is a breaking change.

Please provide more details

[bogdanm]

If you make a change to IAR we MUST run tests against IAR. This is a breaking change.

+1. Removing --vla is likely to break some user code.

[0xc0170]

+1. Removing --vla is likely to break some user code.

No it's should not. It was fixed today (--vla was removed) today anyway. This flag was introduced 1 week ago, since then IAR exporters were not much functional (difference in flags, and their consolidation). The vla addition broke the exporters (IAR does not support --c++ and --vla). thus if we use C++, VLA must be disabled (produces error invalid combination --vla and --c++) - this is valid for project files, cmd has different rules

[bogdanm]

this is valid for project files, cmd has different rules

I see, thank you, I wasn't aware of this restriction. It looks like this isn't as risky as I thought it would be.