Re: GDC CI

Am Sat, 05 Sep 2020 10:04:30 + schrieb wjoe: > This thread is a continuation of the conversation "GDC 10.2.1 Released" > in the Announce group here [1]: > To answer your other question: >> We use https://github.com/D-Programming-GDC/gcc for CI, but >> commits will go to the GCC SVN first, s

Re: Including GDC in nixpkgs

Hi Stefan, Am Fri, 20 Sep 2019 10:29:10 + schrieb Stefan Frijters: > As a fan of both D and the nixpkgs package manager I wanted to try and > help include GDC in nixpkgs, but I have been running into some problems. > Thank you a lot for looking at this and helping the D ecosystem! > If any

Re: Installed with sudo apt-get install gdc in Ubuntu 18.04 - Can't compile a simple program.

Am Tue, 06 Aug 2019 12:22:56 + schrieb Stefanos Baziotis: > On Tuesday, 6 August 2019 at 12:02:05 UTC, Boris Carvajal wrote: >> At least gdc from gcc9 doesn't support static foreach, probably it's >> reading imports from other d compiler install. > > Yes it seems so. I installed LDC from sour

Re: Hello world in AAarch64 Debian Buster

Am Tue, 06 Aug 2019 05:13:11 + schrieb Cecil Ward: > I have a raspberry pi 3B+ running raspbian stretch 32-bit with a > containerised guest o/s inside it using systemd-nspawn, the guest o/s > being AAarch64 Debian Buster. > > Inside AAarch64 Debian Buster, I run the following from the shell a

Re: Is there a GDC solution that can substitute rdmd ? Something like #!/usr/bin/gdc

Am Thu, 27 Jun 2019 17:11:36 + schrieb wjoe: > Hi, > > since D is now a GCC built-in D appears as a nice replacement for shell > scripts. > > I'm *not* looking for a dub solution as dub is something that needs to > be installed. > > A web search found a wrapper script for GCC which imitates

Re: GDC 9 and ARM Cortex-M

Am Sun, 19 May 2019 06:54:14 + schrieb Timo Sintonen: > I am updating my toolset and libraries to GCC/GDC 9.1 release. First > impression is that druntime needs more work than with previous versions. > Many places to change and even compiler crashes when compiling some > files. > > Before I l

Re: GDC android/ios support status ?

Am Tue, 30 Apr 2019 06:16:00 + schrieb ChangLoong: > On Tuesday, 23 April 2019 at 23:45:05 UTC, Iain Buclaw wrote: >> >> It's been applied to gcc-trunk, it'll be in the RC snapshot, >> which should be available some time this week. > > Great work, I can install it from Debian experimental, b

Re: GDC MINGW BUILD: version (Windows) NOT DEFINED

Am Sun, 23 Dec 2018 01:21:22 + schrieb MINGW-USER: > It seems version (Windows) is not defined into the compiler gdc.exe gdc > (GCC) 9.0.0 20181221 (experimental) > built with msys2/mingw-w64 on Windows 10. > > The trouble appears while building libdruntime > > EXAMPLE: libphobos\libdruntime

Re: Using GCC's builtin alloca without the C standard library

Am Mon, 23 Jul 2018 01:35:02 + schrieb Mike Franklin: > I'd like to be able to use GCC's `__builtin_alloca` without the C > standard library. > Just import gcc.builtins for all GCC builtins: import gcc.builtins; void main() { auto foo = __builtin_alloca(10)

Re: How to report code generation weirdness

Am Tue, 20 Mar 2018 23:06:23 + schrieb Cecil Ward: > How do I report some extremely weird (useless) code generated by GDC > when the -O3 option is used? (bizarre rats’ nest of conditional jumps). > [I am an experienced professional asm programmer, now retired.] > > The D source is short, fort

Re: bugzilla.gdcproject.org: No confirmation mail; cpuid.d:838:17: error: PIC register clobbered by 'ebx' in ' asm'

Am Sun, 25 Feb 2018 00:05:44 + schrieb kdevel: > > but gdc (GCC 4.9.4) complains: > > dotbench.d:65:11: Fehler: basic type expected, not foreach > static foreach (s; typenames) { > ^ > dotbench.d:65:11: Fehler: no identifier for declarator _error_ > static foreach (s; ty

Re: bugzilla.gdcproject.org: No confirmation mail; cpuid.d:838:17: error: PIC register clobbered by 'ebx' in ' asm'

Am Thu, 22 Feb 2018 21:34:34 + schrieb kdevel : > On Thursday, 22 February 2018 at 19:52:12 UTC, Johannes Pfau > wrote: > > I've pushed an update to the gdc-4.9 branch. Please report back > > whether this fixes the issue. > > Not really: &g

Re: bugzilla.gdcproject.org: No confirmation mail; cpuid.d:838:17: error: PIC register clobbered by 'ebx' in ' asm'

Am Wed, 21 Feb 2018 21:31:41 + schrieb kdevel : > On Wednesday, 21 February 2018 at 07:58:29 UTC, Johannes Pfau > wrote: > > Am Mon, 19 Feb 2018 19:43:49 + > > schrieb kdevel : > > [...] > > > I'll submit a fix later today or tomorrow. &g

Re: bugzilla.gdcproject.org: No confirmation mail; cpuid.d:838:17: error: PIC register clobbered by 'ebx' in ' asm'

Am Mon, 19 Feb 2018 19:43:49 + schrieb kdevel : > I do not get a confirmation email from bugzilla after entering my > e-mail address here: > https://bugzilla.gdcproject.org/createaccount.cgi > > I tried to build patched versions of GCC 4.8.5 and 4.9.4 but this > happened: > > .../gcc-4.8.

Re: Porting GDC to Yocto project

Am Thu, 15 Feb 2018 15:26:46 + schrieb boolangery : > Hi, > > Is somebody tried to use GDC in Yocto Project ? > (https://www.yoctoproject.org) > > Thanks As far as I know nobody tried that so far. However, I think yocto uses glibc so it shouldn't be difficult for X86/64 and ARM/AArch64 tar

Re: GDMD

Am Wed, 31 Jan 2018 05:46:37 + schrieb Tony : > On Wednesday, 31 January 2018 at 05:44:44 UTC, Tony wrote: > > > which Ubuntu package would I need to install to get it, or > > should it be there now? > > Or do I need a newer version of GDC? > > It is probably not available in ubuntu pa

Re: D in GCC ... 7.3?

Am Fri, 26 Jan 2018 19:38:23 + schrieb John Gabriele : > Just saw the [GCC 7.3 release notice][1], but didn't see any > mention of D or GDC in the [GCC v7 CHANGES doc][2]. > > What GCC version do you think will come stock with GDC? > > [1]: https://gcc.gnu.org/ml/gcc/2018-01/msg00197.html >

Re: Set-up Buildbot for GDC

Am Thu, 07 Dec 2017 21:30:04 + schrieb David J Kordsmeier : > On Friday, 7 July 2017 at 00:05:16 UTC, Iain Buclaw wrote: > > On 7 July 2017 at 01:37, Johannes Pfau via D.gnu > > wrote: > >> Am Fri, 7 Jul 2017 01:12:03 +0200 > >> schrieb "Iain Bucl

Re: Optimization of proposed lambda expression for upcoming DIP

Am Fri, 10 Nov 2017 02:33:41 + schrieb David Nadlinger : > On Friday, 10 November 2017 at 02:26:46 UTC, Michael V. Franklin > wrote: > > `_Dmain` is equivalent, as I expected, but what's going on with > > `main`? Anything to be concerned about? > > I think these are just the getter and s

CI: GCC no longer publishes .bz2 tarballs

I just updated the gdc-6 branch in my repo to gcc 6.4.0 and the CI started to fail downloading the tarball. Turns out that the .bz2 tarball was replaced with a .tar.xz tarball for gcc 6.4.0 and I guess it'll be similar for all new releases: ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/r

Re: ARM Cortex-M Broken Binaries with -O2 and -O3 (-fschedule-insns)

Am Sat, 22 Jul 2017 08:11:28 + schrieb Mike : > On Friday, 21 July 2017 at 23:44:53 UTC, Mike wrote: > > > However, I'm getting broken binaries with -O2 and -O3. I've > > nailed the culprit down to -fschedule-insns (i.e. if I add > > -fno-schedule-insns to -O2 or -O3, the binary works fine

Re: ARM Cortex-M Broken Binaries with -O2 and -O3 (-fschedule-insns)

Am Fri, 21 Jul 2017 23:44:53 + schrieb Mike : > My stm32 demo has now been updated and working with GDC/GCC > 7.1.0. Thanks for all your improvements. > > However, I'm getting broken binaries with -O2 and -O3. I've > nailed the culprit down to -fschedule-insns (i.e. if I add > -fno-sched

Re: ARM Cortex-M Broken Binaries with -O2 and -O3 (-fschedule-insns)

Am Sat, 22 Jul 2017 07:07:33 + schrieb Timo Sintonen : > On Saturday, 22 July 2017 at 01:11:02 UTC, Mike wrote: > > On Friday, 21 July 2017 at 23:44:53 UTC, Mike wrote: > > > >> I'm getting broken binaries with -O2 and -O3. I've nailed the > >> culprit down to -fschedule-insns (i.e. if I a

Re: Set-up Buildbot for GDC

Am Fri, 7 Jul 2017 01:12:03 +0200 schrieb "Iain Buclaw via D.gnu" : > On 7 July 2017 at 00:57, Johannes Pfau via D.gnu > wrote: > > Am Fri, 7 Jul 2017 00:52:20 +0200 > > schrieb Johannes Pfau : > > > >> Am Thu, 6 Jul 2017 10:06:4

Re: Set-up Buildbot for GDC

Am Fri, 7 Jul 2017 00:52:20 +0200 schrieb Johannes Pfau : > Am Thu, 6 Jul 2017 10:06:45 +0200 > schrieb "Iain Buclaw via D.gnu" : > > > > > I've turned on gridview, and it looks like something close to what > > you are asking I think. > > &g

Re: Set-up Buildbot for GDC

Am Thu, 6 Jul 2017 10:06:45 +0200 schrieb "Iain Buclaw via D.gnu" : > > I've turned on gridview, and it looks like something close to what you > are asking I think. > > https://buildbot.dgnu.org/#/grid?branch=master > Looks great! BTW: Any idea why buildbot built only 7 builds this time? The

Re: Can't make use of any headers

Am Thu, 06 Jul 2017 14:26:08 + schrieb jallersma : > Perhaps I have a bit of a noob question, but how come I cannot > use any of the GTKd headers on GCD? On DMD there's no header that > works. I tried to use dub to install the GTKD libraries, but > without any luck. Everytime I try to compi

Re: Set-up Buildbot for GDC

Am Wed, 5 Jul 2017 12:18:28 +0200 schrieb Johannes Pfau : > Am Tue, 4 Jul 2017 23:05:23 +0200 > schrieb Johannes Pfau : > > > I'll try to setup a local builder for debugging later this week or > > next weekend and see if I can reduce some bugs. > > The ARM conf

Re: Set-up Buildbot for GDC

Am Tue, 4 Jul 2017 23:05:23 +0200 schrieb Johannes Pfau : > I'll try to setup a local builder for debugging later this week or > next weekend and see if I can reduce some bugs. The ARM config patch problem can be fixed by including arm-protos.h: #include "config.h" #includ

Re: Set-up Buildbot for GDC

Am Tue, 4 Jul 2017 20:42:52 +0200 schrieb "Iain Buclaw via D.gnu" : > > How do these look? > > https://www.scaleway.com/armv8-cloud-servers/ > > They also have ARMv7's too, I'm currently paying around 18€ a month > for the current linode box - 50G SSD, 4G memory, 2x cores. For the > same price

Re: Set-up Buildbot for GDC

Am Sun, 02 Jul 2017 19:53:05 + schrieb Iain Buclaw : > Hi, > > After some lamenting I've finally gotten round to setting up a > buildbot for gdc. > > https://buildbot.dgnu.org > > Fitted with a smorgasbord of cross compiler builds, all of them > are broken in one way or another, given the

Re: Testing GDC (GCC 7.1) on Runtime-less ARM Cortex-M

Am Wed, 28 Jun 2017 12:56:40 + schrieb Mike : > On Wednesday, 28 June 2017 at 11:19:10 UTC, Mike wrote: > > > I'd be glad to do some troubleshooting if you have any ideas. > > I just checked in a branch that will compile with a desktop GDC > compiler in case someone wants to give it a try

Re: Testing GDC (GCC 7.1) on Runtime-less ARM Cortex-M

Am Wed, 28 Jun 2017 12:27:17 + schrieb Mike : > Does that indicate a backend problem? If you look at my previous > post, linking was also quite high at 33s. Probably. AFAIR -fsyntax-only includes all frontend processing so the long runtime is likely due to the optimization phases, assemblin

Re: Testing GDC (GCC 7.1) on Runtime-less ARM Cortex-M

On Wednesday, 28 June 2017 at 11:19:10 UTC, Mike wrote: I'd be glad to do some troubleshooting if you have any ideas. But I may not get to it right away as I will be traveling for a few weeks. Mike Are we sure this is a frontend problem? Have you already tried -fsyntax-only to remove the

Re: Testing GDC (GCC 7.1) on Runtime-less ARM Cortex-M

Am Sun, 25 Jun 2017 10:53:35 + schrieb Mike : > > I'm not really interested in that because its too blunt of an > instrument. I'd like to use TypeInfo, but only if I'm doing > dynamic casts or other things that require such runtime > information. Also, I'd only want the TypeInfo for the

Re: GDC 5.1.0 fails building.

Am Thu, 20 Apr 2017 07:42:39 + schrieb Jens Bauer : > On Thursday, 20 April 2017 at 07:06:40 UTC, Iain Buclaw wrote: > > On 20 April 2017 at 08:05, Jens Bauer via D.gnu > > wrote: > >> > >> It turns out that GDC-5 will not build ... > >> register_main_translation_unit > >> is not a member

Re: Can't seem to compile on Arch Linux with gdc

Am Fri, 31 Mar 2017 09:11:06 + schrieb Guillaume Chatelet : > I can add a symbolic link to > /usr/lib/gcc/x86_64-pc-linux-gnu/6.3.1/libgcc.a in /usr/lib but > is this the right fix? This is because the GCC package in archlinux has been updated to GCC 6.3.1 but GDC has not been updated and w

Re: GDC 5.4.0 and 6.3.0 not available in Travis CI?

Am Sun, 19 Mar 2017 06:04:35 + schrieb Jeremy DeHaan : > I've updated a Travis CI script to test my project against the > new 2.068.2 GDC versions, but 5.4.0 and 6.3.0 don't seem to be > available. When Travis runs, I get a `Failed to download > 'http://gdcproject.org/downloads/binaries/x86

Re: GDC Pre-Built 6.3.0: Fails during linking stage (liblto_plugin.so)

Am Tue, 14 Mar 2017 23:56:42 + schrieb Maxwell Flynn : > I have been attempting since yesterday evening to compile a D > project of mine on my new Raspberry Pi Zero W. I downloaded the > latest `arm-linux-gnueabi` binary, extracted it, and added it to > my path. Then, I made a makefile to c

Re: [Bug 231] Some template mixins symbols get defined in output object files, although they shouldn't

Am Wed, 25 Jan 2017 16:32:53 + schrieb dan : > i long for the day when gtkd is just a package that i can > install The future is already here - it's just not very evenly distributed. ;-) https://packages.debian.org/stretch/libgtkd-3-0 https://packages.debian.org/stretch/libgtkd-3-dev LDC on

Re: [Bug 231] Some template mixins symbols get defined in output object files, although they shouldn't

Am Wed, 25 Jan 2017 04:10:49 + schrieb dan : > On Saturday, 1 October 2016 at 09:35:22 UTC, Johannes Pfau wrote: > > http://bugzilla.gdcproject.org/show_bug.cgi?id=231 > > > > Johannes Pfau changed: > > > >What|R

Re: Helloworld fails to link on Debian

Am Thu, 22 Dec 2016 18:39:42 + schrieb Sebastien Alaiwan : > $ cat hello.d > import std.stdio; > > int main() > { >writefln("Hello, world"); >return 0; > } > > $ gdc hello.d > /usr/bin/ld: /tmp/cc03E6ZO.o: relocation R_X86_64_PC32 against > symbol > `_D3std6format18__T10FormatSpecT

Re: Travis CI binutils is too old for new binary releases

Am Fri, 9 Dec 2016 18:15:56 +0100 schrieb Johannes Pfau : > I just tested the new binaries with DMD/travis-CI and of course the > build failed immediately: > > https://travis-ci.org/dlang/dmd/jobs/182649710 > > It looks like this is a binutils bug: > https://gcc.gnu.org/bug

Travis CI binutils is too old for new binary releases

I just tested the new binaries with DMD/travis-CI and of course the build failed immediately: https://travis-ci.org/dlang/dmd/jobs/182649710 It looks like this is a binutils bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57017 So I rerun the test with the sysrooted toolchain (this toolchain i

Re: Accessing peripheral registers - the next version

Am Wed, 31 Aug 2016 19:06:37 + schrieb Timo Sintonen : > On Wednesday, 31 August 2016 at 10:12:21 UTC, Johannes Pfau wrote: > > >> There was @disable this(this) > >> This prevents to use a location as argument to a function, > >> like: > >> print

Re: Accessing peripheral registers - the next version

Am Wed, 31 Aug 2016 12:28:58 + schrieb Timo Sintonen : > On Wednesday, 31 August 2016 at 10:12:21 UTC, Johannes Pfau wrote: > > Am Wed, 31 Aug 2016 09:07:49 + > > schrieb Timo Sintonen : > > > > > >> > >> The original functions had force_inl

Re: Accessing peripheral registers - the next version

Am Wed, 31 Aug 2016 09:07:49 + schrieb Timo Sintonen : > Some thing that I have noticed in the original struct definition > > > struct Volatile(T) { > > T raw; > > nothrow: > > @disable this(this); > > A opAssign(A)(A a) { volatileStore(&raw, a); return a; } > > T loa

Re: Accessing peripheral registers - the next version

Am Sun, 28 Aug 2016 09:28:24 + schrieb Timo Sintonen : > I just translated my sample program and everything seems to work > in my limited tests. Here is a simplified example of an uart: > > alias uarttype = uartreg*; > enum uarttype uart1=cast (uarttype)0x40011000; > enum uarttype uart2=cast

Re: Accessing peripheral registers - the next version

Am Sat, 27 Aug 2016 08:05:08 + schrieb Timo Sintonen : > [...] > I did some simple tests and this seems to work. > > My question is: is this the way we should go? Yes, I think this is the best way to implement a volatile type. It is a natural replacement for volatile variables as it can be u

Re: Where is the GDC binaries for Windows targeting windows?

Am Thu, 25 Aug 2016 19:26:26 + schrieb Sai : > > So basically the problem is that these binaries are simply not > > linked on the download page. > > > Could someone please explain the reason why the windows binaries > are not linked on the download page? Is this because they are not > s

Re: Final steps for shared library support

Am Sun, 22 May 2016 20:41:03 +0200 schrieb Johannes Pfau : > > 2) We have to call _d_dso_registry once from every shared library and >from the main executable: >* DMD emits a weak function _d_dso_init into every object file. > Additionally it adds a weak reference t

Re: Where is the native gdc compiler for Windows?

Am Sat, 21 May 2016 21:11:29 + schrieb Richard Delorme : > I cannot find it here: > http://gdcproject.org/downloads > > The tables untitled "Windows X86 64bit (x86_64-w64-mingw32)" and > its 32 bit alter ego only list cross-compilers for arm. > In the release archive, I found this one: > ftp

Final steps for shared library support

I've opened this pull request to finish the shared library support: https://github.com/D-Programming-GDC/GDC/pull/214 These are the remaining problems: 1) We have to find all ModuleInfos in any shared library or in the main executable (in the main executable even for statically linked libdr

Re: Adding support for mingw-w64 and winpthread

Am Wed, 11 May 2016 09:26:12 + schrieb Vincent R : > On Wednesday, 30 March 2016 at 12:05:27 UTC, Vincent R wrote: > > On Wednesday, 30 March 2016 at 11:44:41 UTC, Johannes Pfau > > wrote: > >> Am Wed, 30 Mar 2016 08:27:27 + > >> schrieb Vincent R : >

Re: Adding support for mingw-w64 and winpthread

Am Wed, 30 Mar 2016 08:27:27 + schrieb Vincent R : > make[1]: Entering directory > '/home/19013692/tmp/wxd/src/Samples/Controls' > make[1]: Nothing to be done for 'all'. > make[1]: Leaving directory > '/home/19013692/tmp/wxd/src/Samples/Controls' > make -C Dialogs > make[1]: Entering directo

Re: GDMD D port ready for alpha-testing

Am Sun, 27 Mar 2016 13:36:19 +0200 schrieb Johannes Pfau : > Am Sun, 27 Mar 2016 04:25:27 + > schrieb Basile B. : > > > On Saturday, 26 March 2016 at 10:09:10 UTC, Johannes Pfau wrote: > > > I've finally finished the D port of GDMD and pushed everything >

Re: GDMD D port ready for alpha-testing

Am Sun, 27 Mar 2016 13:36:19 +0200 schrieb Johannes Pfau : > Am Sun, 27 Mar 2016 04:25:27 + > schrieb Basile B. : > > > On Saturday, 26 March 2016 at 10:09:10 UTC, Johannes Pfau wrote: > > > I've finally finished the D port of GDMD and pushed everything >

Re: GDMD D port ready for alpha-testing

Am Sun, 27 Mar 2016 13:31:34 +0200 schrieb Johannes Pfau : > Am Sun, 27 Mar 2016 08:35:00 + > schrieb Vladimir Panteleev : > > > > I'm not sure this approach is the best - I think unescaping and > > splitting should be done in one pass. Essentially, I think &

Re: GDMD D port ready for alpha-testing

Am Sun, 27 Mar 2016 04:25:27 + schrieb Basile B. : > On Saturday, 26 March 2016 at 10:09:10 UTC, Johannes Pfau wrote: > > I've finally finished the D port of GDMD and pushed everything > > including a detailed README to > > https://github.com/D-Programming-GDC/G

Re: GDMD D port ready for alpha-testing

Am Sun, 27 Mar 2016 08:35:00 + schrieb Vladimir Panteleev : > Thanks for working on this :) > > On Saturday, 26 March 2016 at 22:37:53 UTC, Johannes Pfau wrote: > > I didn't realize response file parsing is that important for > > windows, thanks for letting me k

Re: GDMD D port ready for alpha-testing

Am Sat, 26 Mar 2016 10:35:44 + schrieb Vladimir Panteleev : > On Saturday, 26 March 2016 at 10:09:10 UTC, Johannes Pfau wrote: > > I've finally finished the D port of GDMD and pushed everything > > including a detailed README to > > https://github.com/D-Progr

Re: GDMD D port ready for alpha-testing

Am Sat, 26 Mar 2016 11:09:10 +0100 schrieb Johannes Pfau : > I've finally finished the D port of GDMD and pushed everything > including a detailed README to > https://github.com/D-Programming-GDC/GDMD/tree/dport > > All parameters are tested for simple cases but in complex

GDMD D port ready for alpha-testing

I've finally finished the D port of GDMD and pushed everything including a detailed README to https://github.com/D-Programming-GDC/GDMD/tree/dport All parameters are tested for simple cases but in complex combinations there could still be some unknown bugs. I think the D port should already be m

Re: Adding support for mingw-w64 and winpthread

Am Fri, 25 Mar 2016 09:15:06 + schrieb Vincent R : > > So the main question is: can we simply ditch gcc.gthreads and > > inline the code into rt.monitor? > > Thanks for all this information and it seems your knowledge is > far beyond mine so I cannot answer your last question but from >

Re: Adding support for mingw-w64 and winpthread

Am Thu, 24 Mar 2016 11:12:20 +0100 schrieb "Iain Buclaw via D.gnu" : > On 24 March 2016 at 10:52, Vincent R via D.gnu > wrote: > > > Hi, > > > > I would like to generate gdc compiler on msys2/mingw-w64 platform. > > The build system on msys2 uses archlinux build architecture and the > > build fi

Re: Inquiring about cross compilation

Am Mon, 29 Feb 2016 08:35:52 + schrieb Adrian Matoga : > $ dub build > --compiler=/opt/arm-linux-gnueabihf/bin/arm-linux-gnueabihf-gdc > > This can even build vibe.d apps for RPi, provided that you have > all target .so files (AFAIK these are libevent, libevent_pthread, > libssl and libcry

Travis-CI compilers, LATEST file

I just realized I/we totally forgot to answer Martin Nowaks request to update the http://gdcproject.org/downloads/LATEST file to 5.2.0. IIRC we decided some time ago that users should use the GCC version matching their system GCC. What would this mean for Travis-CI? What's the system GCC version f

Re: versions for thumb and thumb-2 instruction sets

Am Sat, 06 Feb 2016 13:58:17 -0800 schrieb Dan Olson : > Hi Iain, Johannes. I'm asking here because I don't expect anybody > else is playing with thumb instructions. > > Both GDC and LDC have version ARM_Thumb defined for original thumb > (call it thumb-1) and thumb-2. But there is no way to te

Re: Build gdc on Windows - GDB compatibility

Am Fri, 05 Feb 2016 11:06:16 + schrieb Vadim Lopatin : > On Wednesday, 3 February 2016 at 13:50:56 UTC, Johannes Pfau > wrote: > > (Pre-)Alpha quality binaries are available, but we don't want to > > advertise these on the homepage: > > ftp://ftp.gdcproject.

Re: Build gdc on Windows

Am Wed, 03 Feb 2016 10:51:11 + schrieb Vadim Lopatin : > On Wednesday, 3 February 2016 at 07:54:07 UTC, Iain Buclaw wrote: > > On 3 Feb 2016 3:10 am, "Carl Sturtivant via D.gnu" > > wrote: > >> > >> I'd like to build gdc to be compatible with the Mingw-w64 > >> 64-bit gcc on > > Windows

Re: Build gdc on Windows

Am Wed, 3 Feb 2016 09:00:37 +0100 schrieb "Iain Buclaw via D.gnu" : > On 3 Feb 2016 8:54 am, "Iain Buclaw" wrote: > > > > On 3 Feb 2016 3:10 am, "Carl Sturtivant via D.gnu" > > > wrote: > > > > > > I'd like to build gdc to be compatible with the Mingw-w64 64-bit > > > gcc on > Windows. (Buil

Re: getopt errors

Am Fri, 22 Jan 2016 11:32:30 + schrieb Sebastiaan Koppe : > On Friday, 22 January 2016 at 10:06:01 UTC, Johannes Pfau wrote: > > defaultGetoptPrinter is not yet available in the phobos version > > used by GDC. GDC uses phobos version 2.066, > > defaultGetoptPrint

Re: getopt errors

Am Thu, 21 Jan 2016 12:06:18 + schrieb Sebastiaan Koppe : > This code: > > bool time; > string fileIn; > string fileOut; > > auto helpInformation = getopt( > args, > "time", "Show timing information", &time, > "i|input", "Inpu

Re: DMD to GDC option converter

Am Fri, 11 Dec 2015 17:54:38 + schrieb Basile B. : > On Friday, 11 December 2015 at 17:51:52 UTC, Basile B. wrote: > > On Friday, 11 December 2015 at 17:39:04 UTC, Thomas Brix Larsen > > wrote: > >> On Friday, 11 December 2015 at 17:17:24 UTC, Basile B. wrote: > >>> [...] > >> > >> gdmd

Re: gdc on sparc with debian-linux problem.

Am Wed, 02 Dec 2015 17:04:57 + schrieb Ish : > Trying to install gdc on Sparc box with (gcc 4.6.3, see below). > > $ uname -a > Linux cps-pe101d24518 3.2.0-4-sparc64-smp #1 SMP Debian > 3.2.68-1+deb7u2 sparc64 GNU/Linux > > $ gcc --version > gcc (Debian 4.6.3-14) 4.6.3 > Copyright (C) 2011

Re: Crash when iterating over files with foreach and std.file.dirEntries on Windows?

Am Mon, 16 Nov 2015 03:08:39 + schrieb Jeremy DeHaan : > I'm wondering if anyone has experienced a crash when using > dirEntries to iterate over files. This is for the Windows 32 bits > build of gdc from the gdc downloads page and it happens for both > the 5.2.0 and 4.9.3 gcc versions (I ha

Re: error: symbol (longsymbol) is already defined

Am Fri, 13 Nov 2015 03:28:01 + schrieb Ellery Newcomer : > On Wednesday, 11 November 2015 at 13:48:16 UTC, Johannes Pfau > wrote: > > Am Tue, 10 Nov 2015 05:14:48 + > > schrieb Ellery Newcomer : > > > >> On Monday, 9 November 2015 a

Re: error: symbol (longsymbol) is already defined

Am Tue, 10 Nov 2015 05:14:48 + schrieb Ellery Newcomer : > On Monday, 9 November 2015 at 08:53:30 UTC, Iain Buclaw wrote: > > > > Instead of funneling blame, this could be resolved in the move > > to 2.067 > > (maybe just skipping to 2.068). The complete > > > The warning still appears i

Re: Trying to generate gdc for mingw-w64(x86 and x64) using msys2

Am Tue, 10 Nov 2015 08:03:02 + schrieb Vincent R : > On Monday, 9 November 2015 at 16:47:20 UTC, Johannes Pfau wrote: > > Am Mon, 09 Nov 2015 00:22:52 + > > schrieb Vincent R : > > > >> I tried a last time before and I managed to make it work not > >

Re: Trying to generate gdc for mingw-w64(x86 and x64) using msys2

Am Mon, 09 Nov 2015 00:22:52 + schrieb Vincent R : > I tried a last time before and I managed to make it work not > completely but at least I can see a hello world application on > the console: > > > $ gdc -o main.exe main.d > $ ./main.exe > Hello D-World! > > It's late now but I have som

Re: Trying to generate gdc for mingw-w64(x86 and x64) using msys2

Am Thu, 05 Nov 2015 18:42:32 + schrieb Vincent R : > On Thursday, 5 November 2015 at 14:27:20 UTC, Vincent R wrote: > > [...] > > I tried to add a version(MinGW) inside core.sys.posix.sys.types > to just declare pthread_key_t but it didn't work because I still > have exactly the same erro

Re: Trying to generate gdc for mingw-w64(x86 and x64) using msys2

Am Thu, 05 Nov 2015 12:42:08 + schrieb Vincent R : > Hi, > > I would like to generate a d compiler targeting mingw-w64 using > the msys2 build system. > So I have installed msys2 (posix emulation like cygwin) as shown > here: http://msys2.github.io/ and I have installed necessary > package

Re: Does gdb support D enums?

Am Wed, 21 Oct 2015 11:45:58 +0300 schrieb drug : > Using gdb `print` instead of enum value I see `incomplete type`. Did > I miss something? (I use gdb 7.10 from ttp://ftp.gnu.org/gnu/gdb/) > > Thanks Which gdc branch/version? And please provide a testcase as I can't reproduce this bug with a si

Re: import problems

Am Tue, 13 Oct 2015 10:16:11 + schrieb John Colvin : > On Tuesday, 13 October 2015 at 10:09:03 UTC, John Colvin wrote: > > Where does the information > > sorry, pressed enter by accident. > > What is the process by which gdc knows what the default import > path for object.d is? > It use

Re: releases

Am Tue, 6 Oct 2015 18:13:26 +0200 schrieb "Iain Buclaw via D.gnu" : > > I hope you are not backporting latest master to those branches > too. ;-) > I didn't have a look at the latest changes yet. Any reason why I shouldn't backport these?

Re: releases

Am Tue, 06 Oct 2015 12:52:23 + schrieb John Colvin : > http://gdcproject.org/downloads are all with gcc 5.2 > > https://github.com/D-Programming-GDC/GDC/releases/tag/v2.066.1_gcc5 > is with gcc 5.1, as is the gdc-5 branch > The gcc.version file is the version tested by the CI systems. This

Re: Which version to use?

Am Thu, 24 Sep 2015 03:07:53 + schrieb Jeremy DeHaan : > On (my version of) Linux, gdc has an official apt repository, but > there also exists a download page with what appears to be a much > more recent version of gdc. So..which one should I use? I'd like > to have pre-built binaries for m

Download restructuring

I've now moved most downloads & integrated the 4.9.3 and 5.2.0 releases. Next steps are: - update travis symlinks - delete old folder structure There's one small problem: The Travis links are currently in binaries/$HOST and these host folders should be removed at some point. @Iain shall we move t

Re: Linker errors with i686-w64-mingw32 binaries

Am Mon, 10 Aug 2015 12:36:32 +0200 schrieb "Iain Buclaw via D.gnu" : > On 6 August 2015 at 13:19, Mike Parker via D.gnu > wrote: > > > On Thursday, 6 August 2015 at 11:07:33 UTC, Mike Parker wrote: > > > >> Haven't tried the 64-bit binaries yet, but any attempt to compile > >> an executable with

Re: Restructuring the download archive

Am Sat, 11 Jul 2015 13:37:42 +0200 schrieb "Iain Buclaw via D.gnu" : > On 11 July 2015 at 10:01, Johannes Pfau via D.gnu > wrote: > > > > > Isn't the frontend version usually more important for the user? The > > frontend version determines if user

Re: Restructuring the download archive

Am Fri, 10 Jul 2015 16:26:35 +0200 schrieb "Iain Buclaw via D.gnu" : > > Another question: DMD frontend sub-releases in one folder? > > (2.061|2.061.1|2.061.2) > > > > > I think GCC releases should take precedence over D Frontend and > architecture IMO. As that is the most recognisable (and impor

Restructuring the download archive

I thinks it's time to push some new binary releases to gdcproject.org (gcc-5, intrinsics for checkedint, ...). We should first get some structure into our download archive though: ftp://ftp.gdcproject.org/binaries/ The first question is whether we can break old download links. I've hardcoded

Re: [Testing] Using Travis CI (or better alternative) for master/branch/PR testing

Am Tue, 23 Jun 2015 20:46:41 +0200 schrieb "Iain Buclaw via D.gnu" : > @Johannes, I've created a GDC team on semaphoreci, will add you to it > along with the build configuration I've set-up so far. I imagine > this will be rolled out tomorrow. Let's see how this goes... Sounds great! My semapho

Re: [Testing] Using Travis CI (or better alternative) for master/branch/PR testing

Am Mon, 22 Jun 2015 20:37:40 +0200 schrieb "Iain Buclaw via D.gnu" : > On 22 June 2015 at 19:58, Johannes Pfau via D.gnu > wrote: > > Am Mon, 22 Jun 2015 08:56:53 + > > schrieb "Iain Buclaw" : > > > >> As the autotester seems to be b

Re: GDC phobos source path

Am Tue, 23 Jun 2015 15:37:35 + schrieb "John Colvin" : > How does gdc know where to look for druntime/phobos source code? > I successfully built gdc for the first time on OS X, but it's > looking at completely the wrong source code. > > I have gdc manually (i.e. make install) installed in /

Re: [Testing] Using Travis CI (or better alternative) for master/branch/PR testing

Am Mon, 22 Jun 2015 08:56:53 + schrieb "Iain Buclaw" : > As the autotester seems to be broken indefinitely for the time > being, I've been playing around with Travis for builds. > > https://travis-ci.org/ibuclaw/GDC/branches > > A couple of show stoppers I've been running into: > - Time to

Re: gdc master is broken for arm cross-compilers

Am Tue, 16 Jun 2015 22:05:44 +0200 schrieb Johannes Pfau : > Am Thu, 11 Jun 2015 22:30:39 +0200 > schrieb "Iain Buclaw via D.gnu" : > > > On 11 June 2015 at 20:27, Johannes Pfau via D.gnu > > wrote: > > > > > Some recent change in GDC broke ARM cr

Re: gdc master is broken for arm cross-compilers

Am Thu, 11 Jun 2015 22:30:39 +0200 schrieb "Iain Buclaw via D.gnu" : > On 11 June 2015 at 20:27, Johannes Pfau via D.gnu > wrote: > > > Some recent change in GDC broke ARM cross compiler builds. Same > > error with gcc-5.1 and gcc-4.9: > > > > https:/

gdc master is broken for arm cross-compilers

Some recent change in GDC broke ARM cross compiler builds. Same error with gcc-5.1 and gcc-4.9: https://gist.github.com/jpf91/1de81d6ff55587d702ae I'm not sure if this only happens for ARM cross compilers or for all cross compilers. But it doesn't seem to happen with native builds (or maybe it's

Re: (Probably trivial) arm-none-eabi-gdc building problem

Am Thu, 04 Jun 2015 04:05:39 + schrieb "Mike" : > On Wednesday, 3 June 2015 at 12:54:32 UTC, Johannes Pfau wrote: > > > > That's correct. All ARM GCC compilers can generate code for all > > ARM variants (the hf compiler can generate softfloat code and >

  1   2   3   4   >