On Fri, Nov 22, 2013 at 11:55 AM, Jim Grosbach <[email protected]> wrote: > > On Nov 22, 2013, at 11:43 AM, Renato Golin <[email protected]> wrote: > > On 22 November 2013 14:33, Bernard Ogden <[email protected]> wrote: >> >> Non-Darwin: Arch for cpu specified with -mcpu takes precendence over arch >> specified by -arch/-march >> Darwin: Arch specified with -arch/-march takes precendence over arch >> specified by -mcpu > > > This is ugly, but if it's the expected behaviour in Darwin, I won't cry. > > Jim, you seem to know these corner cases of the Darwin Arch selection, does > that make sense? > > > -mcpu= takes precedence over -arch; however, the slice (cpu subtype in the > MachO file) is still dictated by the -arch setting only. > > Using -march= and -mcpu= at the same time should probably be a hard error. > -march is preferable and 32-bit ARM is the outlier for historical reasons in > preferring -mcpu. I’d love to be able to change that, but it’s likely to be > a hard road. >
Also, welcome to a great example of why -march + -mcpu is confusing and wrong. -eric _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
