Bug 17093 – gdc compilation performance on the Raspbery Pi leaves to be desired
Status
RESOLVED
Resolution
WONTFIX
Severity
enhancement
Priority
P1
Component
tools
Product
D
Version
D2
Platform
Other
OS
Linux
Creation time
2017-01-16T05:15:33Z
Last change time
2019-03-21T08:15:17Z
Assigned to
No Owner
Creator
Ion Todirel
Comments
Comment #0 by iontodirel — 2017-01-16T05:15:33Z
gdc seems much slower than gcc on Raspberry Pi, I don't know what other detail to provide
Comment #1 by iontodirel — 2017-01-16T05:16:07Z
This is a Raspberry Pi 3
Comment #2 by iontodirel — 2017-01-16T05:16:46Z
P.S. running Raspbian Jessie
Comment #3 by ibuclaw — 2017-01-16T21:46:23Z
Any comparative examples of C vs. D would be useful. If it's slow on Raspi, then it'll be slow on any other host system, just not as pronounced.
Assuming you mean time to compile, could be any of three components which it's spending most of it's time in.
1) Compiler:
If here, try compiling with -v -ftime-report -ftime-report-details, and we'll see if there's any semantic / pass that it is taking longer than others.
2) Assembler:
If here, then it's not a bug, and you've just underestimated just how much code is generated. Here's a contrived example: https://goo.gl/Ya6lXB
3) Linker:
Again, it's not a bug. But chances am you are linking to druntime/phobos statically, this is would be a very IO and CPU intensive on a poor Raspi. Compiling with -shared-libphobos should sort that out and bring you back up to speed with gcc. (Debian turns on -shared-libphobos by default, but in upstream for now it is still default disabled while it undergoes more testing).