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

[Daniel Alejandro Benavides D.]

Hello:Excuse me if is wrong to say, but doesn't the specification of Modula-3 explicit about how the UNSAFE stuff is implementation-dependent, that is to say; "it's your decision how to implement it".Thanks in advance
 


    El Domingo 13 de diciembre de 2015 21:20, Jay <jay.krell at cornell.edu> escribió:
 

 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, loopholethat into an address of another type, and dereference that.Not in the backend, but in the Modula-3 code.




_______________________________________________
M3devel mailing list
M3devel at elegosoft.com
https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20151214/5b2f03c7/attachment-0002.html>