On Mon, 21 May 2018, Jeff Law wrote:
> Whether or not a global register is saved in the prologue and restored
> in the epilogue is actually a function of the target's prologue/epilogue
> implementation.
>
> So ISTM this paragraph needs to be refined a bit. Essentially it may or
> may not change t
On 05/10/2018 03:47 AM, Alexander Monakov wrote:
>
>
> On Mon, 23 Apr 2018, Alexander Monakov wrote:
>
>> This rewrites global register vars doc to reflect that the register is no
>> longer
>> reserved exclusively, but in fact is available for general allocation, and
>> also
>> adds the requir
On Mon, 23 Apr 2018, Alexander Monakov wrote:
> This rewrites global register vars doc to reflect that the register is no
> longer
> reserved exclusively, but in fact is available for general allocation, and
> also
> adds the requirement to properly inform the compiler where inline asms are
>
This rewrites global register vars doc to reflect that the register is no longer
reserved exclusively, but in fact is available for general allocation, and also
adds the requirement to properly inform the compiler where inline asms are
accessing the variable.
This:
-@item The register is not saved
