On 25/07/16 14:25, Eric Botcazou wrote: >> If I understand how this is supposed to work then this is not >> future-proof against changes to the architecture. The bottom two bits >> in both AArch32 (arm) and AArch64 are reserved for future use by the >> architecture; they must not be used by software for tricks like this. > > I see, thanks for the info, the value will need to be bumped to 4 then. > > From the definition of TARGET_PTRMEMFUNC_VBIT_LOCATION, I gather that the > MIPS > setting is probably incorrect too and ought to be bumped to 2. >
So does this require that every function have an 8-byte alignment boundary? or just those that appear in nested functions? If the former, how do you get routines written in assembler, or produced by third-party compilers, to comply? R.