digitalmars.D.announce - GDC release 0.20

David Friedman (8/8) Dec 16 2006 Source and binaries here:

Jarrett Billingsley (3/11) Dec 16 2006 Yaaay!
Kirk McDonald (6/16) Dec 16 2006 Excellent! Now I can get to work getting Pyd working on Linux!

Bill Baxter (6/20) Dec 17 2006 Why did you have to wait for GDC to catch up in order to have Pyd for

Kirk McDonald (8/31) Dec 17 2006 Pyd compiles DLL (well, .pyd) files on Windows and .so files on Linux.

Alexander Panek (2/12) Dec 17 2006 Finally! Woohoo! \o/
=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= (11/14) Dec 17 2006 Except for a small glitch with "BSD sed" vs. "GNU sed",
Chad J (4/14) Dec 17 2006 It is 0.177 equivalent!!!11
Thomas Kuehne (15/23) Dec 23 2006 -----BEGIN PGP SIGNED MESSAGE-----

Thomas Kuehne (15/32) Dec 25 2006 -----BEGIN PGP SIGNED MESSAGE-----

Frits van Bommel (9/18) Dec 25 2006 Does GDC's asm not support a more clear

Thomas Kuehne (14/32) Dec 27 2006 -----BEGIN PGP SIGNED MESSAGE-----

Brad Roberts (7/48) Dec 27 2006 I'm not sure which compiler is at 'fault' here, but having them behave

David Friedman <dvdfrdmn users.ess-eff.net> writes:

Source and binaries here:

http://sourceforge.net/project/showfiles.php?group_id=154306

* Updated to DMD 0.177
* Fixes for synchronized code generation
* Better support for cross-hosted builds
* Fixed Bugzilla 307, 375, 403, 575, 578
* Applied Anders Bj�rklund's MacOS X build patches
* SkyOS support will return when GCC 4.1.1 is supported.

Dec 16 2006

"Jarrett Billingsley" <kb3ctd2 yahoo.com> writes:

"David Friedman" <dvdfrdmn users.ess-eff.net> wrote in message 
news:em2j8b$1o17$1 digitaldaemon.com...
 Source and binaries here:

 http://sourceforge.net/project/showfiles.php?group_id=154306

 * Updated to DMD 0.177
 * Fixes for synchronized code generation
 * Better support for cross-hosted builds
 * Fixed Bugzilla 307, 375, 403, 575, 578
 * Applied Anders Bj�rklund's MacOS X build patches
 * SkyOS support will return when GCC 4.1.1 is supported.

Yaaay!

Dec 16 2006

Kirk McDonald <kirklin.mcdonald gmail.com> writes:

David Friedman wrote:
 Source and binaries here:
 
 http://sourceforge.net/project/showfiles.php?group_id=154306
 
 * Updated to DMD 0.177
 * Fixes for synchronized code generation
 * Better support for cross-hosted builds
 * Fixed Bugzilla 307, 375, 403, 575, 578
 * Applied Anders Bj�rklund's MacOS X build patches
 * SkyOS support will return when GCC 4.1.1 is supported.

Excellent! Now I can get to work getting Pyd working on Linux!

-- 
Kirk McDonald
Pyd: Wrapping Python with D
http://pyd.dsource.org

Dec 16 2006

Bill Baxter <dnewsgroup billbaxter.com> writes:

Kirk McDonald wrote:
 David Friedman wrote:
 Source and binaries here:

 http://sourceforge.net/project/showfiles.php?group_id=154306

 * Updated to DMD 0.177
 * Fixes for synchronized code generation
 * Better support for cross-hosted builds
 * Fixed Bugzilla 307, 375, 403, 575, 578
 * Applied Anders Bj�rklund's MacOS X build patches
 * SkyOS support will return when GCC 4.1.1 is supported.

 
 Excellent! Now I can get to work getting Pyd working on Linux!
 

Why did you have to wait for GDC to catch up in order to have Pyd for 
Linux?  Does the DMD compiler for Linux not work?

Supporting GDC is great anyway, I just don't understand why it would be 
a prerequisite for having Pyd on Linux.

--bb

Dec 17 2006

Kirk McDonald <kirklin.mcdonald gmail.com> writes:

Bill Baxter wrote:
 Kirk McDonald wrote:
 David Friedman wrote:
 Source and binaries here:

 http://sourceforge.net/project/showfiles.php?group_id=154306

 * Updated to DMD 0.177
 * Fixes for synchronized code generation
 * Better support for cross-hosted builds
 * Fixed Bugzilla 307, 375, 403, 575, 578
 * Applied Anders Bj�rklund's MacOS X build patches
 * SkyOS support will return when GCC 4.1.1 is supported.

 Excellent! Now I can get to work getting Pyd working on Linux!

 
 Why did you have to wait for GDC to catch up in order to have Pyd for 
 Linux?  Does the DMD compiler for Linux not work?
 
 Supporting GDC is great anyway, I just don't understand why it would be 
 a prerequisite for having Pyd on Linux.
 
 --bb

Pyd compiles DLL (well, .pyd) files on Windows and .so files on Linux. 
DMD is incapable of producing working .so files, at least so far as I 
can tell.

-- 
Kirk McDonald
Pyd: Wrapping Python with D
http://pyd.dsource.org

Dec 17 2006

Alexander Panek <a.panek brainsware.org> writes:

David Friedman wrote:
 Source and binaries here:
 
 http://sourceforge.net/project/showfiles.php?group_id=154306
 
 * Updated to DMD 0.177
 * Fixes for synchronized code generation
 * Better support for cross-hosted builds
 * Fixed Bugzilla 307, 375, 403, 575, 578
 * Applied Anders Bj�rklund's MacOS X build patches
 * SkyOS support will return when GCC 4.1.1 is supported.

Finally! Woohoo! \o/

Dec 17 2006

=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:

David Friedman wrote:

 Source and binaries here:
 
 http://sourceforge.net/project/showfiles.php?group_id=154306

Except for a small glitch with "BSD sed" vs. "GNU sed",
(hardcoded -E parameter should be -r for GNU I think?)
it built OK for MinGW/3.4.2 and Mac OS X 10.3/3.3.6...

As usual, the installer packages are found at:
http://gdcwin.sourceforge.net/ (MinGW / 3.4.2)
http://gdcmac.sourceforge.net/ (Mac OS X 10.3)

Use David's "official" tarball binaries for
MinGW/GCC-3.4.5 or Mac OS X 10.4/GCC-4.0.1 ?
(will be available as packages too, later on)

--anders

Dec 17 2006

Chad J <gamerChad _spamIsBad_gmail.com> writes:

David Friedman wrote:
 Source and binaries here:
 
 http://sourceforge.net/project/showfiles.php?group_id=154306
 
 * Updated to DMD 0.177
 * Fixes for synchronized code generation
 * Better support for cross-hosted builds
 * Fixed Bugzilla 307, 375, 403, 575, 578
 * Applied Anders Bj�rklund's MacOS X build patches
 * SkyOS support will return when GCC 4.1.1 is supported.

It is 0.177 equivalent!!!11

YES!

Thank you David!

Dec 17 2006

Thomas Kuehne <thomas-dloop kuehne.cn> writes:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Friedman schrieb am 2006-12-17:
 Source and binaries here:

 http://sourceforge.net/project/showfiles.php?group_id=154306

 * Updated to DMD 0.177
 * Fixes for synchronized code generation
 * Better support for cross-hosted builds
 * Fixed Bugzilla 307, 375, 403, 575, 578
 * Applied Anders Bj�rklund's MacOS X build patches
 * SkyOS support will return when GCC 4.1.1 is supported.

I've updated the DStress pages for GDC-0.20
http://dstress.kuehne.cn/www/dstress.html
http://dstress.kuehne.cn/www/gdc-0.20.html

Something funny is going on with the assembler, especially the f*
instructions. (Please ignore failing MMX & SSE tests for now, they are
under heavy construction.)

Thomas


-----BEGIN PGP SIGNATURE-----

iD8DBQFFjdi4LK5blCcjpWoRAgqOAJ9yPiu4op+knCk/p0TApkwVM/zDIQCeOITp
8//FyoHtMkjincW67P+dufU=
=sxwR
-----END PGP SIGNATURE-----

Dec 23 2006

Thomas Kuehne <thomas-dloop kuehne.cn> writes:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Kuehne schrieb am 2006-12-24:
 David Friedman schrieb am 2006-12-17:
 Source and binaries here:

 http://sourceforge.net/project/showfiles.php?group_id=154306

 * Updated to DMD 0.177
 * Fixes for synchronized code generation
 * Better support for cross-hosted builds
 * Fixed Bugzilla 307, 375, 403, 575, 578
 * Applied Anders Bj?rklund's MacOS X build patches
 * SkyOS support will return when GCC 4.1.1 is supported.

 I've updated the DStress pages for GDC-0.20
 http://dstress.kuehne.cn/www/dstress.html
 http://dstress.kuehne.cn/www/gdc-0.20.html

 Something funny is going on with the assembler, especially the f*
 instructions. (Please ignore failing MMX & SSE tests for now, they are
 under heavy construction.)

Neither floating point nor MMX nor SSE instructions where the cause 
but the "cpuid" feature tests.

I had to replace

	asm{ cpuid; }

with
	asm{db 0x53; cpuid; db 0x5B;}

Thomas


-----BEGIN PGP SIGNATURE-----

iD8DBQFFj/XZLK5blCcjpWoRAlnMAJ9LwhWiZXx+0ex3tMPWhinKCL0wtQCfZhJ2
PrDwAkrWsHZIr1VMr/2p+Pc=
=8+Vu
-----END PGP SIGNATURE-----

Dec 25 2006

Frits van Bommel <fvbommel REMwOVExCAPSs.nl> writes:

Thomas Kuehne wrote:
 Neither floating point nor MMX nor SSE instructions where the cause 
 but the "cpuid" feature tests.
 
 I had to replace
 
 	asm{ cpuid; }
 
 with
 	asm{db 0x53; cpuid; db 0x5B;}

Does GDC's asm not support a more clear
	asm {push EBX; cpuid; pop EBX; }
?

Or for that matter, doesn't it know what registers are changed by 
instructions so it can save the ones it needs to preserve (DMD does that 
IIRC)?
(Or if it isn't sure, doesn't it at least make sure they get pushed & 
popped as a precaution?)

Dec 25 2006

Thomas Kuehne <thomas-dloop kuehne.cn> writes:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frits van Bommel schrieb am 2006-12-25:
 Thomas Kuehne wrote:
 Neither floating point nor MMX nor SSE instructions where the cause 
 but the "cpuid" feature tests.
 
 I had to replace
 
 	asm{ cpuid; }
 
 with
 	asm{db 0x53; cpuid; db 0x5B;}

 Does GDC's asm not support a more clear
 	asm {push EBX; cpuid; pop EBX; }
 ?

It does, however if I compile with "-fPIC" GDC errors with:
error: PIC register `ebx' clobbered in `asm'

 Or for that matter, doesn't it know what registers are changed by 
 instructions so it can save the ones it needs to preserve (DMD does that 
 IIRC)?
 (Or if it isn't sure, doesn't it at least make sure they get pushed & 
 popped as a precaution?)

DMD preserves them via copying to the stack. GDC doesn't preserve them
and apparently only knowns the clobbering rules for some instructions
(e.g. pop EBX) but not others (e.g. push EBX).

Thomas


-----BEGIN PGP SIGNATURE-----

iD8DBQFFkkZKLK5blCcjpWoRAnsHAJ4wH4Z6+SiJkllM6S48AXEJCRqWcwCfXUww
sV5ZrY1kUPbnov5YXAkcTWc=
=7zkJ
-----END PGP SIGNATURE-----

Dec 27 2006

Brad Roberts <braddr puremagic.com> writes:

On Wed, 27 Dec 2006, Thomas Kuehne wrote:

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 Frits van Bommel schrieb am 2006-12-25:
 Thomas Kuehne wrote:
 Neither floating point nor MMX nor SSE instructions where the cause 
 but the "cpuid" feature tests.
 
 I had to replace
 
 	asm{ cpuid; }
 
 with
 	asm{db 0x53; cpuid; db 0x5B;}

 Does GDC's asm not support a more clear
 	asm {push EBX; cpuid; pop EBX; }
 ?

 
 It does, however if I compile with "-fPIC" GDC errors with:
 error: PIC register `ebx' clobbered in `asm'
 
 Or for that matter, doesn't it know what registers are changed by 
 instructions so it can save the ones it needs to preserve (DMD does that 
 IIRC)?
 (Or if it isn't sure, doesn't it at least make sure they get pushed & 
 popped as a precaution?)

 
 DMD preserves them via copying to the stack. GDC doesn't preserve them
 and apparently only knowns the clobbering rules for some instructions
 (e.g. pop EBX) but not others (e.g. push EBX).
 
 Thomas
 
 
 -----BEGIN PGP SIGNATURE-----
 
 iD8DBQFFkkZKLK5blCcjpWoRAnsHAJ4wH4Z6+SiJkllM6S48AXEJCRqWcwCfXUww
 sV5ZrY1kUPbnov5YXAkcTWc=
 =7zkJ
 -----END PGP SIGNATURE-----

I'm not sure which compiler is at 'fault' here, but having them behave 
differently with the same block of asm code on the same platform seems 
like a violation of the intent of having asm be part of the language spec.  
A bug needs to be filed against one of the two compilers.

Later,
Brad

Dec 27 2006

D Programming

C/C++ Programming

Other

digitalmars.D.announce - GDC release 0.20