Change in coreboot[master]: docs/coding_style: Clarify use of GCC extensions

[Julius Werner (Code Review)]

Julius Werner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/63660 )

Change subject: docs/coding_style: Clarify use of GCC extensions
......................................................................

Patch Set 3:

(1 comment)

Patchset:

PS2:
> Is there value in a section on what to do if a developer encounters a GCC extension that their compi […]

I mean, that would only be applicable to HOSTCC code, I think... for coreboot code I think it's well-established that crossgcc is the only compiler we care about and we should keep it that way. (The folks that care about clang should figure out how they want that to work once it is more stable... without integrating anything into Jenkins it's going to be hard to keep any support working long term.)

It would certainly not hurt to have more documentation on crossgcc and general compiler expectations, but I think at that point it's getting pretty far away from "coding style"... maybe that would fit better somewhere under getting_started.