Re: Forcing GNAT to use 32-bit load/store instructions on ARM?

[Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP>]

On 2014-07-06, MatthiasR <MatthiasR@invalid.invalid> wrote:
> They recommend to use a temporary variable to ensure an access to the record 
> variable as a whole.
>
> That is not really elegant, because records with representation clauses, 
> directly mapped onto hardware registers, look like the most natural way to 
> access these registers. Reading Ada books, one even could get the impression 
> that record represenation clauses are made primarily for this purpose.
> Unfortunately there seem to be no way to force a specific access width, so 
> this feature is not really useable (without the mentioned workaround with 
> the temporary variable) on architectures where the allowed access width is 
> not uniform over the whole address range.
>

Totally agree.

In addition, Ada needs syntax/semantics to update multiple bitfields
within a record as one write operation without having to use a
temporary. The size of the write (assuming the record itself was
marked as Atomic) would be the size of the record.

In that way, you could (finally) get rid of temporary variables and C
style bitmasks when updating registers.

Simon.

-- 
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world