[M3devel] atomic problem

Jay K jay.krell at cornell.edu
Mon Feb 8 00:51:11 CET 2010


I don't like such "non-determinism".

  Granted, it isn't really non-deterministic.

I want to know which other machines things will run on, not

just have them run on the machine on which they are built.

Building things yourself is nice, but not doing it is also nice too.

 And not doing it on every machine even if you do build it yourself

   is nice.

 

 

Which "reminds", or rather "convinces" me..we should just

never do native builds in m3cc and m3gdb.

We should pass imho what we believe to be the

platform, but with carefully chosing which processor.

Gotta test like every platform though.

 

 

 - Jay

 


From: hosking at cs.purdue.edu
Date: Sun, 7 Feb 2010 14:32:44 -0500
To: jay.krell at cornell.edu
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] atomic problem

I think -march=native works too assuming you are on a modern x86.






Antony Hosking | Associate Professor | Computer Science | Purdue University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484



On 7 Feb 2010, at 14:08, Jay K wrote:

It looks like i586 suffices. I checked that in to the LINUXLIBC6 config file.
Probably I386_DARWIN, FreeBSD4, NetBSD2_i386 etc. need updating.
We can probably adjust m3cc/m3makefile.
The platforms.quake file won't do, since native builds don't use it.
 
 - Jay
 


From: hosking at cs.purdue.edu
Date: Sun, 7 Feb 2010 13:55:13 -0500
To: jay.krell at cornell.edu
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] atomic problem

-march=i686





Antony Hosking | Associate Professor | Computer Science | Purdue University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484



On 7 Feb 2010, at 08:39, Jay K wrote:

ok, better now, but:
 
== package /home/jay/dev2/cm3/m3-sys/m3staloneback ==
 +++ /cm3/bin/cm3   -build -DROOT=/home/jay/dev2/cm3 -DCM3_VERSION_TEXT=d5.8.2 -
DCM3_VERSION_NUMBER=050802 -DCM3_LAST_CHANGED=2009-07-15 +++
--- building in LINUXLIBC6 ---
ignoring ../src/m3overrides
new source -> compiling Main.m3
 -> linking m3back
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an
d_and_8'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an
d_or_4'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an
d_sub_1'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_bool_com
pare_and_swap_4'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an
d_or_1'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an
d_or_2'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an
d_sub_4'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an
d_add_4'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_bool_com
pare_and_swap_1'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an
d_add_2'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an
d_xor_1'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an
d_and_4'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_bool_com
pare_and_swap_8'
/cm3/pkg/m3core/LINUXLIBC6/libm3core.so: undefined reference to `__sync_fetch_an


 - Jay

 


From: jay.krell at cornell.edu
To: hosking at cs.purdue.edu; m3devel at elegosoft.com
Date: Sun, 7 Feb 2010 13:16:45 +0000
Subject: Re: [M3devel] atomic problem

Probably an out of date m3cg.
I'll see.
 
 - Jay
 


From: jay.krell at cornell.edu
To: hosking at cs.purdue.edu; m3devel at elegosoft.com
Date: Sun, 7 Feb 2010 13:09:57 +0000
Subject: [M3devel] atomic problem

Could be I'm out of date or building in the wrong order.
I'll maybe dig into it.
Linux/x86:
 
new source -> compiling AtomicWideChar.m3
../LINUXLIBC6/AtomicWideChar.m3 => ../src/atomic/Atomic.mg: In function 'AtomicW
ideChar__Load':
../LINUXLIBC6/AtomicWideChar.m3 => ../src/atomic/Atomic.mg:0: internal compiler
error: in expand_expr_real_1, at expr.c:7290
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
  m3_backend => 4
m3cc (aka cm3cg) failed compiling: AtomicWideChar.mc
new source -> compiling hand.c
new source -> compiling dtoa.c
new source -> compiling libgcc.c
new source -> compiling RTIOc.c



 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100207/809c065b/attachment-0002.html>


More information about the M3devel mailing list