http://blog.gmane.org/gmane.comp.lang.d.gnu hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.lang.d.gnu/903 <pre>I was planning to install FreeBSD, but I was wondering if x32-abi(i.e. x86-64 but using fast 32bit pointers) is a supported configuration together with D in linux using the D gnu compiler, then it would be the incentive to go linux instead. if not supported, is it planned to be supported? </pre> Franz 2012-05-26T10:00:48 http://comments.gmane.org/gmane.comp.lang.d.gnu/899 <pre>I don't know if anyone saw my bug on core.thread.Fiber under MinGW64. I'm curious to know if anyone else can reproduce it? - Manu </pre> Manu 2012-05-24T09:42:12 http://comments.gmane.org/gmane.comp.lang.d.gnu/897 <pre>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 Changes: * Fixes __t.0 undefined references with interfaces. * Fixes 32-</pre> Daniel Green 2012-05-14T04:20:09 http://comments.gmane.org/gmane.comp.lang.d.gnu/893 <pre>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 { &lt; at &gt;property Vec vPosition() { return mPosition; } &lt; at &gt;property Vec vPosition( const ref Vec value ) { return mPosition = value; } private: Vec mPosition; } === Now, this code should output either "2 2" or "3 3" depending on the time. However, on release builds this code will output "0 0" every time it is run. This seems to happen regardless of the optimization level (we have tried with -O1 and -O3). Some things to note is that the bug will NOT occur if any of the following is true: - We compile the code in debug mode. - We specify a constant known at compile time (eg. "true") instead of the non-deterministic time value. - We save the vector into a temp</pre> SebastianA 2012-05-10T14:18:59 http://comments.gmane.org/gmane.comp.lang.d.gnu/878 <pre>** 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/ GDC binary https://bitbucket.org/goshawk/gdc/downloads/gcc-4.6.1-tdm64-1-gdc-7e1a98da2769-20120428-D2.058.7z Known issues: * May br</pre> Daniel Green 2012-04-28T17:08:17 http://comments.gmane.org/gmane.comp.lang.d.gnu/869 <pre>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 Known issues: * May break TDM64 C++. * Field-less structs will thro</pre> Daniel Green 2012-04-27T03:19:02 http://comments.gmane.org/gmane.comp.lang.d.gnu/868 <pre> 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. </pre> Joseph Rushton Wakeling 2012-04-26T22:12:30 http://comments.gmane.org/gmane.comp.lang.d.gnu/863 <pre>I've built gtkD as a static library using gdc, but whenever I try to link libgtkd.a into another program, I get dozens of errors like /path/to/libgtkd.a(HScrollbar.o)(.data+0x80)undefined reference to `____t.0' I'm using the latest gdc from github, with the latest gcc snapshot, on both 32- and 64-bit linux. Could this be related to https://bitbucket.org/goshawk/gdc/issue/284/ and if so, is there any way around it? --Ed </pre> Ed McCardell 2012-04-23T23:30:25 http://comments.gmane.org/gmane.comp.lang.d.gnu/858 <pre>Hey Daniel, I've tried your new mingw-gdc repository but I've had some patching failures: $ hg qclone https://bitbucket.org/venix1/mingw-gdc $ cd mingw-gdc $ hg qpush -a Errors: ------------------------------------------------------------------ applying documents applying patches applying dmain unable to find 'gcc/d/d-spec.c' for patching 8 out of 8 hunks FAILED -- saving rejects to file gcc/d/d-spec.c.re j unable to find 'gcc/d/lang.opt' for patching 1 out of 1 hunks FAILED -- saving rejects to file gcc/d/lang.opt.re j unable to find 'libphobos/Makefile.am' for patching 1 out of 1 hunks FAILED -- saving rejects to file libphobos/Makefil e.am.rej unable to find 'libphobos/libdruntime/Makefile.am' for patching 2 out of 2 hunks FAILED -- saving rejects to file libphobos/libdrun time/Makefile.am.rej unable to find 'libphobos/libdruntime/Makefile.in' for patching 3 out of 3 hunks FAILED -- saving rejects to file libphobos/libdrun time/Makefile.in.rej unable to find 'libphobos/libdruntime/rt/dmain2.d' for patc</pre> Andrej Mitrovic 2012-04-23T17:02:57 http://comments.gmane.org/gmane.comp.lang.d.gnu/845 <pre>Hello all, Is gdmd missing the -od flag (outputdir for built objects) that dmd provides? If so, is there a plan to add it? Thanks &amp; best wishes, -- Joe </pre> Joseph Rushton Wakeling 2012-04-15T21:17:50 http://comments.gmane.org/gmane.comp.lang.d.gnu/842 <pre>Hello all, I've come across a compilation problem with gdc 4.6.3 (the package in the Ubuntu repositories). I have some code, available from https://github.com/WebDrake/SampleD ... which uses in contracts on some class functions: a base class has one in contract for one of its methods (lines 16-26), and a subclass overrides this method and provides its own in contract (lines 50-66). If I compile without the -release switch, e.g. gdmd -O -inline -oftest sampled.d I get the following error: sampled.d:50: Error: function [classname].select cannot get frame pointer to __require Is this an instance of this bug? https://bitbucket.org/goshawk/gdc/issue/78/d1-d2-in-out-contract-inheritance ... or something different? The code compiles without problem using regular dmd. 'Tis a shame, as in general I'm finding gdc much preferable to dmd -- the code it produces is much, much faster! Thanks and best wishes, -- Joe </pre> Joseph Rushton Wakeling 2012-04-13T21:36:54 http://comments.gmane.org/gmane.comp.lang.d.gnu/833 <pre>I have a request for the next binary release of GDC. Can it please contain binaries for the libs in etc.c...? Trying to track down compatible versions of zlib, curl, sqlite for MinGW64 is surprisingly difficult to do! &gt;_&lt; These modules are packaged with phobos as if they're standard issue, so can we please consider the libs standard issue too? Otherwise they're pretty useless. </pre> Manu 2012-04-06T14:57:19 http://comments.gmane.org/gmane.comp.lang.d.gnu/790 <pre>Hello all, First, congratulations to the GDC team -- I'm playing with D for the first time in quite a while thanks to the up-to-date gdc 4.6 packages in the upcoming Ubuntu LTS release. It's great to see that D 2.0 now has this kind of mainstream distro support. Anyway, a question about the gdc versus gdmd interfaces to the compiler. I've noticed that compiling with the options gdmd -O -release -inline produces a much faster executable (about twice as fast) as the typical gcc-style options I would use, gdc -O2 [or -O3] Can anyone advise on appropriate gdc options to pick up the same speed level? Thanks and best wishes, -- Joe </pre> Joseph Rushton Wakeling 2012-04-02T15:48:49 http://comments.gmane.org/gmane.comp.lang.d.gnu/785 <pre>As the topic suggests, I'm looking for instructions to get a cross-compiler working on Linux and the ones in the Wiki are fairly outdated, referring to old versions of D2 and GCC. The compiler actually builds, but it cannot build Phobos, with these lines of errors: /home/marco/Entwicklung/D/gdc/dev/gcc-4.6.2/windows/./gcc/gdc -B/home/marco/Entwicklung/D/gdc/dev/gcc-4.6.2/windows/./gcc/ -L/home/marco/Entwicklung/D/gdc/dev/gcc-4.6.2/windows/i686-mingw32/winsup/mingw -L/home/marco/Entwicklung/D/gdc/dev/gcc-4.6.2/windows/i686-mingw32/winsup/w32api/lib -isystem /home/marco/Entwicklung/D/gdc/dev/gcc-4.6.2/winsup/mingw/include -isystem /home/marco/Entwicklung/D/gdc/dev/gcc-4.6.2/winsup/w32api/include -B/usr/i686-mingw32/bin/ -B/usr/i686-mingw32/lib/ -isystem /usr/i686-mingw32/include -isystem /usr/i686-mingw32/sys-include -Wall -g -frelease -O2 -nostdinc -pipe -fdeprecated -I ../../../libphobos -I ./i686-mingw32 -fintfc-file=import/core/sys/windows/dbghelp.di -fsyntax-only ../../../libphobos/core/sys/windows/dbg</pre> Marco Leise 2012-03-29T18:34:42 http://comments.gmane.org/gmane.comp.lang.d.gnu/781 <pre>Morning all, I've done a flat copy of all immediately addressable wiki pages from bitbucket over to github. https://github.com/D-Programming-GDC/GDC/wiki There are some alterations that may be required, especially on the "how to build" bits that are on most pages. I will have time to look at them later, but would be grateful if any of the original contributors would update their bits first. Regards Iain </pre> Iain Buclaw 2012-03-26T17:37:44 http://comments.gmane.org/gmane.comp.lang.d.gnu/735 <pre>I thought about supporting emulated tls a little. The GCC emutls.c implementation currently can't work with the gc, as every TLS variable is allocated individually and therefore we don't have a contiguous memory region for the gc. I think these are the possible solutions: * Try to fix GCCs emutls to allocate all tls memory for a module (application/shared object) at once. That's the best solution and native TLS works this way, but I'm not sure if we can extract enough information from the runtime linker to make this work (we need at least the combined size of all tls variables). * Provide a callback in GCC's emutls which is called after every allocation. This could call GC.addRange for every variable, but I guess adding huge amounts of ranges is slow. * Make it possible to register a custom allocator for GCC's emutls (not sure if possible, as this would have to be set up very early in application startup). Then allocate the memory directly from the GC (but this memory should only be scan</pre> Johannes Pfau 2012-03-18T11:32:05 http://comments.gmane.org/gmane.comp.lang.d.gnu/728 <pre>I don't have libgmp-3.dll, and every attempt I make to get it results in what would seem to be an incompatible version of the DLL, producing the message: "The procedure entry point __gmp_get_memory_functions could not be located..." The version of gmp distributed with the current version of mingw is libgmp-10.dll. Older packages don't appear to be compatible. Consider dropping the libgmp-3.dll you build against in the bin/ directory alongside gdc.exe? </pre> Manu 2012-03-16T11:39:54 http://comments.gmane.org/gmane.comp.lang.d.gnu/724 <pre>I'm picking up some old issues from bugzilla, this one is worth having a community review. http://d.puremagic.com/issues/show_bug.cgi?id=1949 Should hidden GCC features be imported from a magic module provided by gcc.* packages - or should the implementation be re-written using pragmas instead? This is what LDC currently does (all of which would be possible to do in GDC): http://www.dsource.org/projects/ldc/wiki/Docs#Pragmas Discuss. :) </pre> Iain Buclaw 2012-03-12T15:35:52 http://comments.gmane.org/gmane.comp.lang.d.gnu/717 <pre>I find myself really wishing for proper multiple return values almost every day, particularly when I work with maths heavy code, and especially for efficiently returning error codes in functions I'd rather not throw from. Many maths-y functions return some sort of pair; intersections return (ray, t) or something of that type. I'm finding HEAPS of SIMD functions want to return pairs (unpacks in particular): int4 (low, hight) = unpack(someShort8); Currently I have to duplicate everyting: int4 low = unpackLow(someShort8); int4 high = unpackHigh(someShort8); I'm getting really sick of that, it feels so... last millennium. The point of 'proper' multiple return values is to return each value in registers, in its own register type, using exactly the same register assignment pattern as when passing args TO functions. I don't think this causes any side effects to the ABI, since the arg registers are already volatile across function calls in the first place. It just means that the returned-to function can find its re</pre> Manu 2012-03-08T19:40:20 http://comments.gmane.org/gmane.comp.lang.d.gnu/711 <pre>Hi there, just want to inform the list for whoever who's interested how to compile GDC on Mac OS X Lion because it was tricky. The first steps do as explained here: https://bitbucket.org/goshawk/gdc/wiki/Home#!installation Be sure to have the libraries installed via MacPorts. Clone the repository, download and unpack gcc. Before configuring, completely disable the AVX check in the i386 GCC driver by editing gcc/config/i386/driver-i386.c commenting out the line has_avx = ecx &amp; bit_AVX; We have to do this because the assembler (as) delivered with MacOS doesn't support AVX. You could also try to use clang as assembler but it doesn't support the full AVX instruction set. Also you could try the binutils of MacPorts (GAS), but this doesn't - unfortunately - support reliable Mach-O output :-( Now use as configure line: ./configure --enable-languages=d --disable-bootstrap --disable-nls --prefix=/opt/local --with-bugurl="https://bitbucket.org/goshawk/gdc/issues" --enable-checking=yes --disable-libg</pre> André Wösten 2012-02-26T11:23:48 http://comments.gmane.org/gmane.comp.lang.d.gnu/705 <pre>As recently discussed in a pull request it would be great if we could make it easier to port druntime to different architectures. Special casing every C library, every architecture and every OS using version blocks could lead to difficult to maintain code, so we need a better solution. As far as I can see, the biggest differences are caused by different C libraries, not by different architectures (except 32bit vs 64 bit differences). For example glibc headers seem to be very similar for arm and x86, but bionic vs. glibc brings more differences. Bionic initially didn't support anything wchar_t related, so core.stdc.wchar_ and core.stdc.wctype couldn't work with android at all. And C libraries vary even more in the subset of posix functionality they support. We need a directory scheme to support * Different C libraries * on different OS (glibc/bsd glibc/linux) * on the same OS (glibc on linux, bionic on linux, uclibc on linux, ...) * Different architectures (ARM, X86, MIPS, PPC, SH4, ...) I propose </pre> Johannes Pfau 2012-02-25T17:19:03 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lang.d.gnu