multiple build failures with XCC toolchain

[zephyrbot]

Reported by Andrew Boie:

We are experiencing multiple build failures with the XCC toolchain.

Steps to reproduce:

1. Set up XCC on local workstation, you need both Xplorer 7.0.4 and 6.0.4
2. export ZEPHYR_GCC_VARIANT=xcc
3. Run sanitycheck --all

This bug needs to be split by root cause, there are a few of them:

1. Use of self-referential designated initializers for wait queue members of kernel objects, like fifo/lifos
2. Designated initializers for anonymous structs/unions
3. { 0 } initializers where the first member of the initialized struct is not a scalar type
4. Some problem with D_233L which results in 'file truncted' errors

It is NOT necessarily the case that we should just change all our code to work around limitations of this compiler.
We may instead pull up to a newer XCC version for all SOC targets and use its built-in clang support.

End result of this bug is all issues fixed, sanitycheck --all passes, or bugs filed for individual issues.

(Imported from Jira ZEP-2517)

[zephyrbot]

by Andrew Boie:

Just to be clear: I don't want us doing further code changes to work around the current XCC compiler limitations.
New XCC release RG.7 is forthcoming end of August. I want to see us standardize on this release, in Clang mode.
We will drop all support for XCC versions before RG.7.
Once we have that version of XCC running in Clang mode we can again look any code changes (if necessary) but most of the problems should go away.

[ManojSubbarao]

@rgundi what is the status?

[rgundi]

@ManojSubbarao we are not actively working on this anymore. As Andrew says we will reevaluate once we move to Clang.

[ManojSubbarao]

closing this issue since it's not relevant at this point of time. will revisit when needed.