[M3devel] atomic operations in cm3 (also fails on AMD64_LINUX)

[Daniel Alejandro Benavides D.]

Hi all:
Thanks for the message and now I caught it, I have found a thesis on the <* FIELDS *> specification feature, perhaps would be a nice idea to use it to verify the trees in both Olivetti and CM3 front end, and to convert back and forth (for instance when select ESC-ing a program so just doing it once and for all is faster).

And thinking it more, I guess similarly this could be the way to watch the back end to reconstruct/infer the types same from the gcc assembly (and the CLEF tree) and compare and match if they truly match to prove it's correct.

Thanks in advance

--- El mar, 28/2/12, Antony Hosking <antony.hosking at gmail.com> escribió:

De: Antony Hosking <antony.hosking at gmail.com>
Asunto: Re: [M3devel] atomic operations in cm3 (also fails on AMD64_LINUX)
Para: "Daniel Alejandro Benavides D." <dabenavidesd at yahoo.es>
CC: "Dragiša Durić" <dragisha at m3w.org>, "m3devel" <m3devel at elegosoft.com>, "Jay K" <jay.krell at cornell.edu>
Fecha: martes, 28 de febrero, 2012 15:46

It is the front end outputting badly typed IR.
On Feb 28, 2012, at 1:09 PM, Daniel Alejandro Benavides D. wrote:
Hi all:
I don't understand it, what is breaking, the compiler front end, the backend or both or what else? Besides platform feature instability, means that you are doing UNSAFE MODULEs? Question, is your machine SMP? I have one 32 and 64 UP LINUXLIBC6 capable, does it matter if is in one or in the other?
Thanks in advance

--- El mar, 28/2/12, Dragiša Durić <dragisha at m3w.org> escribió:

De: Dragiša Durić <dragisha at m3w.org>
Asunto: Re: [M3devel] atomic operations in cm3 (also fails on AMD64_LINUX)
Para: "Antony Hosking" <antony.hosking at gmail.com>
CC: "m3devel" <m3devel at elegosoft.com>, "Jay K" <jay.krell at cornell.edu>
Fecha: martes, 28 de febrero, 2012 09:08

% cm3--- building in ../AMD64_LINUX ---
new source -> compiling AtomicAddress.m3"../AMD64_LINUX/AtomicAddress.m3", line 3:  18 code generation errors1 error encounterednew exporters -> recompiling AtomicAddress.i3compilation failed => not building program "test"Fatal Error: package build failed
% cat m3makefile import("libm3")
...
Generic_module("Atomic")template("atomic")Atomic("Address")
program ("test")
On Feb 28, 2012, at 2:25 PM, Antony Hosking wrote:
Yes, this is a known bug.
On Feb 28, 2012, at 8:15 AM, Dragiša Durić wrote:
% cm3--- building in ../AMD64_DARWIN ---
new source -> compiling Proxy.m3"../src/Proxy.m3", line 13: warning: not used (JobHandler)1 warning encounterednew source -> compiling AtomicAddress.i3new source -> compiling AtomicAddress.m3"../AMD64_DARWIN/AtomicAddress.m3 => ../src/Atomic.mg", line 52: ********* M3CG_Check ERROR *********** bad stack:  expected [ Int64    ] got [ Addr  Int64   ]

****** runtime error:***    Segmentation violation - possible attempt to dereference NIL***    pc = 0x1002f0838 = Concat + 0x8a in ../src/text/TextCat.m3***
zsh: abort      cm3
On Feb
 27, 2012, at 8:15 AM, Dragiša Durić wrote:
m3-libs/m3core/src/atomic/Atomic.ig is well commented, also.

On Feb 27, 2012, at 1:37 AM, Jay K wrote:
Shows how to use it all.
 
It is disabled. Let's try
 it..




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20120228/1dc64095/attachment-0002.html>