On 22/07/14 16:23, Ramana Radhakrishnan wrote: > > > On 22/07/14 14:14, Kyrill Tkachov wrote: >> Hi all, >> >> In the arm backend we've got this TARGET_UNIFIED_ASM macro that is >> currently on for TARGET_THUMB2 with a comment that says: >> /* We could use unified syntax for arm mode, but for now we just use it >> for Thumb-2. */ >> >> I've been doing some work converting the pre-UAL floating point >> mnemonics to unified syntax and it seems if we were to strictly adhere >> to this TARGET_UNIFIED_ASM I would have to guard those changes, which >> would be somewhat ugly. > > I would just change vfp.md to UAL and expect it to work because GAS > accepts unified syntax for the floating point instructions even without > .syntax unified. > > We need T_U_A until the point of time that the Thumb1 port is converted > to UAL, GAS validated against Thumb1 and the rest of the "arm" port is > converted to UAL and verified with GAS. > > Additionally if someone were to do the full transition, remember that > users need to have a way of mixing non-unified syntax in inline > assembler with unified syntax in the rest of the C code. > > > regards > Ramana > >> >> Is it perhaps time to just drop this and assume unified asm everywhere? >> >> >> Kyrill >> >> > > >
We also need to be able to support User's inline assembly that is not in unified syntax. Though that might be a different issue to the one you're trying to address here. R.