headers
Daniel Green | 14 May 06:20
Picon

MinGW Release. D2.058 x86-64 20120513

Please post all issues in D.gnu or on GDC's site 
https://bitbucket.org/goshawk/gdc

Due to the use of a newer runtime than TDM64-GCC it is **recommended** 
to install a copy specifically for GDC.

Features
  **ALPHA** As in, D2.058 support is still new.
  * D2.058
  * Debug information available using gnu-debuglink.
  * Removed D1(Did anyone use this feature?).
    * Due to current system breaking with repository changes and D1
      being discontinued at the end of the year.
  * binutils with TLS patches
  * mingw-w64-runtime with TLS and stdio fixes.
  * GCC 4.6.1 with TLS patches

Installation instructions:

1. Download and install TDM MinGW64
2. Extract the downloaded archive into the base of the newly installed 
TDM install.

If you've done this before, you can just do step 2.

MinGW64 installer
http://tdm-gcc.tdragon.net/

GDC binary
https://bitbucket.org/goshawk/gdc/downloads/gcc-4.6.1-tdm64-1-gdc-dd401b9-20120513-D2.058.7z
(Continue reading)

Permalink | Reply | 1 comment |
headers
SebastianA | 10 May 17:10

Re: Problem with passing ref parameters to properties

I had not tested the code with DMD. We need x64 support, so we 
need GDC for that at the moment. However, I tried compiling with 
DMD and it seems that the line

t.vPosition = (Clock.currStdTime % 2 == 0) ? Vec(2, 2) : Vec(3, 
3);

does not compile with the latest DMD compiler. I get the error:

test.d(23): Error: not a property t.vPosition

when trying that. If I remove the ternary operator and just 
assign Vec(2, 2) to the property, it works as expected. Am I 
missing something here? Why cannot I write the code as listed 
above?
Permalink | Reply | 1 comment |
headers
SebastianA | 10 May 16:18

Problem with passing ref parameters to properties

We are seeing a problem with passing ref parameters to 
properties. This bug only occurs in certain situations. Consider 
the following code:

====
void runTest()
{
	Thing t;
	t.vPosition = (Clock.currStdTime % 2 == 0) ? Vec(2, 2) : Vec(3, 
3);
	Vec v = t.vPosition;

	outputDebug("%d %d\n", v.x, v.y);
}

struct Vec
{
	int x;
	int y;
}

struct Thing
{
	@property Vec vPosition() { return mPosition; }
	@property Vec vPosition( const ref Vec value ) { return 
mPosition = value; }

private:
	Vec mPosition;
}
(Continue reading)

Permalink | Reply | 1 comment |
headers
d-bugmail | 5 May 13:54

[Issue 1] asm enter and leave bug

http://d.puremagic.com/issues/show_bug.cgi?id=1

klickverbot <code <at> klickverbot.at> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |code <at> klickverbot.at

--- Comment #10 from klickverbot <code <at> klickverbot.at> 2012-05-05 04:55:15 PDT ---
(In reply to comment #9)
> Merge pull request #924 from donc/D1uninitialized
> 
> Heisenbug: D1-only uninitialized variable

The GitHub Bugzilla hook script must have misparsed that message – can anyone
see how?

--

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
Permalink | Reply | 0 comments |
headers
d-bugmail | 4 May 19:40

[Issue 1] asm enter and leave bug

http://d.puremagic.com/issues/show_bug.cgi?id=1

--- Comment #9 from github-bugzilla <at> puremagic.com 2012-05-04 10:41:20 PDT ---
Commit pushed to dmd-1.x at https://github.com/D-Programming-Language/dmd

https://github.com/D-Programming-Language/dmd/commit/5a062e8d544a5c66ecfe0df456096ad12f6963eb
Merge pull request #924 from donc/D1uninitialized

Heisenbug: D1-only uninitialized variable

--

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
Permalink | Reply | 0 comments |
headers
Daniel Green | 1 May 16:31
Picon

Re: MinGW Release. D2.058 x86-64 20120428

On 5/1/2012 1:53 AM, Iain Buclaw wrote:
> no _Dmodule_ref would probably mean no object_.d was compiled in.

In D2.058, the _Dmodule_ref code was moved to minfo.d.  I didn't 
properly move the GNU specific stuff on the first build, problem didn't 
surface until I compiled it with MinGW.

They reduced it to OSX, Posix for including _Dmodule_ref.  Which is why 
linux didn't exhibit the same problems.

I added it back but there's a chance the 32-bit library wasn't updated 
properly.
Permalink | Reply | 1 comment |
headers
Daniel Green | 1 May 06:37
Picon

Re: MinGW Release. D2.058 x86-64 20120428

On 4/30/2012 2:49 PM, Manu wrote:
>     I also built sqlite, but it's complaining with lots of:
>
>     C:\Users\MANUEV~1\AppData\Local\Temp\cclkNCic.o: In function
>     `D4demu5tools8sqlitedb8SQLiteDB6AttachMFAxaAxaZE4demu5tools5error9ErrorCode':
>     D:\Projects\SuperEmu/Source/Tools/SQLiteDB.d:57: undefined reference
>     to `sqlite3_exec'
>     C:\Users\MANUEV~1\AppData\Local\Temp\cclkNCic.o: In function
>     `D4demu5tools8sqlitedb8SQLiteDB5CloseMFZv':
>     D:\Projects\SuperEmu/Source/Tools/SQLiteDB.d:46: undefined reference
>     to `sqlite3_close'
>     C:\Users\MANUEV~1\AppData\Local\Temp\cclkNCic.o: In function
>     `D4demu5tools8sqlitedb8SQLiteDB4OpenMFAxaZE4demu5tools5error9ErrorCode':
>     D:\Projects\SuperEmu/Source/Tools/SQLiteDB.d:34: undefined reference
>     to `sqlite3_open'
>     etc...
>
>
>     Any ideas?

Build order?  binutils isn't smart(purposefully so?) when it comes to 
symbol resolution.  The symbol must be declared after it is used.  I 
would check the -v output and see where your library is in relation to 
the object file.

>
>     Here's how I built sqlite, in case I did something wrong:
>     gcc -c sqlite3.c -m64 -O3  -> sqlite3.o
>     ar rs libsqlite.a sqlite3.o    -> sqlite.a
(Continue reading)

Permalink | Reply | 1 comment |
headers
Daniel Green | 30 Apr 17:33
Picon

Re: MinGW Release. D2.058 x86-64 20120428

On 4/30/2012 6:18 AM, Manu wrote:
> I guess the etc.c... libs didn't make the cut :(

It was sort of an intermittent release, to get it out and tested.

To update the lib status, zlib is already part of libgphobos2.a.  If you 
inspect the library you'll see it's object files.  If you're having 
specific zlib errors, you should share them.

sqlite.o is easy enough to build and can be put into libgphobos.a. 
Being public domain helps, I'll add it to the build process.

Curl is the only tricky one.  It actually has configuration options and 
probably dependencies.  Is there a list of what features D requires curl 
to support?
Permalink | Reply | 4 comments |
headers
Daniel Green | 28 Apr 19:08
Picon

MinGW Release. D2.058 x86-64 20120428

** Fixes, previous unresolved _Dmodule_ref **

Please post all issues in D.gnu or on GDC's site 
https://bitbucket.org/goshawk/gdc

Due to the use of a newer runtime than TDM64-GCC it is **recommended** 
to install a copy specifically for GDC.

Features
  **ALPHA** As in, D2.058 support is still new.
  * D2.058
  * Debug information available using gnu-debuglink.
  * Removed D1(Did anyone use this featuer?).
    * Due to current system breaking with repository changes and D1
      being discontinued at the end of the year.
  * binutils with TLS patches
  * mingw-w64-runtime with TLS and stdio fixes.
  * GCC 4.6.1 with TLS patches

Installation instructions:

1. Download and install TDM MinGW64
2. Extract the downloaded archive into the base of the newly installed 
TDM install.

If you've done this before, you can just do step 2.

MinGW64 installer
http://tdm-gcc.tdragon.net/
(Continue reading)

Permalink | Reply | 2 comments |
headers
Dejan Lekic | 27 Apr 10:16
Picon
Gravatar

Re: GDC 4.7.0 and Ubuntu

Joseph Rushton Wakeling wrote:

> On 17/04/12 22:56, Iain Buclaw wrote:
>> I can't reproduce this or the bug in puremagic on my build, so I will
>> go on the assumption this will be fixed in the 4.7.0 package due to
>> ship with Ubuntu at the end of the month.
> 
> Given that 12.04 has just officially been released -- what's the situation
> of
> GDC 4.7.0 in the current release of Ubuntu?  The current package is still
> 4.6.3.

Joseph, for now you have to build GCC with GDC included yourself, until GCC 
people merge GDC with the GCC. That will happen probably with 4.8 because 
there are various issues (legal, code standards, etc)...
Permalink | Reply | 4 comments |
headers
Daniel Green | 27 Apr 05:19
Picon

MinGW Release. D2.058 x86-64

Please post all issues in D.gnu or on GDC's site 
https://bitbucket.org/goshawk/gdc

Due to the use of a newer runtime than TDM64-GCC it is **recommended** 
to install a copy specifically for GDC.

Features
  **ALPHA** As in, D2.058 support is still new.
  * D2.058
  * Debug information available using gnu-debuglink.
  * Removed D1(Did anyone use this featuer?).
    * Due to current system breaking with repository changes and D1
      being discontinued at the end of the year.
  * binutils with TLS patches
  * mingw-w64-runtime with TLS and stdio fixes.
  * GCC 4.6.1 with TLS patches

Installation instructions:

1. Download and install TDM MinGW64
2. Extract the downloaded archive into the base of the newly installed 
TDM install.

If you've done this before, you can just do step 2.

MinGW64 installer
http://tdm-gcc.tdragon.net/

GDC binary
https://bitbucket.org/goshawk/gdc/downloads/gcc-4.6.1-tdm64-1-gdc-7e1a98da2769-20120426-D2.058.7z
(Continue reading)

Permalink | Reply | 4 comments |

Gmane