> OK, that sounds doable. But if -Wa is going to be used as a matter of
> course to pass arch/fpu options, we should get rid of all #ifdef's
> against things like __thumb2__, as they can be out of sync.

First of all users would have to recognize and accept that they can't
pass -march=armv4 to compiler and at the same time instruct assembler to
generate thumb. Because it would undermine whole idea. Then keep in mind
that -march=armv4 would never define __thumb2__, so that as long as we
look at __ARM_ARCH__ (and not __ARM_MAX_ARCH__) when choosing between
.thumb and .code 32, it's not a problem from preprocessor viewpoint. But
removing those #ifdefs would prevent user from specifying min==max==7
and thumb. In other words logic around __thumb2__ might have to be
refined, but I think it can still be useful.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to