Hi,
On Thu, Aug 11, 2011 at 4:22 PM, Richard Sandiford
wrote:
> Dave Martin writes:
>> However, there's not really anything fundamentally
>> architecture-specific about this problem, and ideally the solution and
>> the directives should not be architecture-specific either.
>> One option which ap
Dave Martin writes:
> However, there's not really anything fundamentally
> architecture-specific about this problem, and ideally the solution and
> the directives should not be architecture-specific either.
> One option which appeals to me is to have some directives which can
> exist across all ar
Hi all,
On ARM, we've now hit the problem a few times of temporarily
overriding the assembler state (or rather, not being able to do this
reliably). For example, sometimes there's a need to assemble a few
instructions for a different architecture version so we can optionally
execute or skip them
