This is the mail archive of the
mailing list for the GCC project.
Re: [ARM] Is TARGET_UNIFIED_ASM still needed?
- From: Ramana Radhakrishnan <ramana dot radhakrishnan at arm dot com>
- To: Kyrill Tkachov <kyrylo dot tkachov at arm dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Tue, 22 Jul 2014 16:23:33 +0100
- Subject: Re: [ARM] Is TARGET_UNIFIED_ASM still needed?
- Authentication-results: sourceware.org; auth=none
- References: <53CE63D1 dot 4010000 at arm dot com>
On 22/07/14 14:14, Kyrill Tkachov wrote:
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
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.
Is it perhaps time to just drop this and assume unified asm everywhere?