https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60821
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
For at least 5.x+ the following has been done.
1. note that "-arch xxxx" has a different semantic in the Apple driver from the
general semantic of GCC options. I.E. it is *meant* to be used more than once,
thus there's no positional significance to a given instance.
This has no meaning with the regular GCC driver as noted in the various
comments.
2. If multiple arch flags are presented that conflict (e.g. -arch i386 -arch
x86_64) then a diagnostic is issued and *ALL* the -arch entries are discarded
(the compiler produces code according to its default multilib).
- given (1), there is no reasonable strategy for deciding a "winner" so all
lose.
- at least, it allows a single -arch xxxx to be used in lieu of the GCC
regular multilib flags.
this is present on all open branches so closing as fixed.
