[M3devel] M3CG loophole operator is not LOOPHOLE (but what?)

[Jay]

I know, but this pattern is pretty rare. 

 - Jay

On Dec 13, 2015, at 1:46 AM, Antony Hosking <hosking at purdue.edu> wrote:

> Excepting that in some cases taking the address may force the value into memory, when it could have stayed in a register.
> The intent is to allow the backend to avoid that.
> 
>> On 11 Dec 2015, at 5:53 PM, Jay K <jay.krell at cornell.edu> wrote:
>> 
>> The right thing to do, really, is take the address of a float, loophole
>> that into an address of another type, and dereference that.
>> Not in the backend, but in the Modula-3 code.
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20151213/ca871b97/attachment-0002.html>