On Sunday, 25 June 2017 at 10:18:04 UTC, Mike wrote:
Compile Speed
=
It takes about 1 minute 30 seconds to build and link the STM32
demo resulting in a 6kB binary. That's pretty bad, but I
suspect that's a DMD CTFE problem.
I'm been informed that this PR
(https://github.com/dla
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
On 25 June 2017 at 13:30, Mike via D.gnu wrote:
> On Sunday, 25 June 2017 at 10:53:35 UTC, Mike wrote:
>
>> 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 inform
On Sunday, 25 June 2017 at 10:53:35 UTC, Mike wrote:
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 types
On Sunday, 25 June 2017 at 10:44:26 UTC, Iain Buclaw wrote:
Out of curiosity, is that the original built binary, or post
trimming
(strip / --gc-sections)?
I'm compiling with -ffunction-sections and -fdata-sections, and
linking with --gc-sections.
There might be a size optimization possibili
On 25 June 2017 at 12:18, Mike via D.gnu wrote:
> This is just an experience report for those who might be interested.
>
> Given this pull request (https://github.com/D-Programming-GDC/GDC/pull/456)
> I thought I'd try testing a more recent GDC with my STM32 demo
> (https://github.com/JinShil/stm3
This is just an experience report for those who might be
interested.
Given this pull request
(https://github.com/D-Programming-GDC/GDC/pull/456) I thought I'd
try testing a more recent GDC with my STM32 demo
(https://github.com/JinShil/stm32f42_discovery_demo) and see what
the state of thing
