https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71104
--- Comment #9 from Marc Glisse <glisse at gcc dot gnu.org> --- (In reply to rguent...@suse.de from comment #8) > Not that I like this proposal at all (given it changes function arg > evaluation order on x86_64). Does it? "the function is evaluated before all its arguments, but any pair of arguments (from the argument list) is indeterminately sequenced" The notation a(b1, b2, b3) means that there is no particular order between b1 and b2, otherwise it would be written a(b, c, d).