https://sourceware.org/bugzilla/show_bug.cgi?id=32073
--- Comment #13 from Jan Beulich <jbeulich at suse dot com> --- (In reply to Maciej W. Rozycki from comment #12) > Where does the notion of using whitespace for argument separation in > macro invocations (as opposed to definitions) come from? I have no idea, and I never really liked it. But I've seen it in actual use, not just once. My vague guess is that comma separation actually was introduced only later, to allow macro uses to look more like insns. > I can see it was you actually who documented this feature in the GAS > manual back in 2022 only. But if GAS does accept whitespace here, then > isn't it just a GAS regression that needs fixing instead? Regression? Afaict this (bad) mode of argument (and parameter) separation has been there forever. It just may not have been properly spelled out in the doc. > Is there any > substantial piece of software out there known to rely on this previously > undocumented feature (and why)? I know we've switched to (consistently) comma separation in the Xen hypervisor only a year or so ago. The origin of Xen is Linux; I didn't extensively check recent Linux, but at least on x86 there are such macro uses. And I can certainly easily spot macro definitions across various architectures where parameters are separated by just blanks. > How does the use of whitespace for > argument separation mix with default values anyway? Not very well, as you apparently inferred. Yet iirc defaults for macro arguments hadn't been there all the time. -- You are receiving this mail because: You are on the CC list for the bug.
