On Wednesday, 14 January 2015 at 14:20:50 UTC, Iain Buclaw via
D.gnu wrote:
Could it be that the entire module trace takes up 128K?
Probably not
very likely. And I doubt the writeLine/write templates
contribute to
much.
Sorry, I didn't see this reply before I submitted my last post.
The
On Wednesday, 14 January 2015 at 13:32:53 UTC, Mike wrote:
Well, I was working a reduced test case and found that it has
something to do with my trace.d file here:
https://github.com/JinShil/stm32f42_discovery_demo/blob/master/source/stm32f42/trace.d
If I add a trace.writeLine("x") in my progr
On 14 January 2015 at 13:32, Mike via D.gnu wrote:
> On Wednesday, 14 January 2015 at 09:04:50 UTC, Mike wrote:
>>
>>
>> Ok, but I have a mess of classes generated by templates (and I love it).
>> Their `name` properties [1] should go in .rodata, right? But why aren't
>> they being put in their o
On Wednesday, 14 January 2015 at 09:04:50 UTC, Mike wrote:
Ok, but I have a mess of classes generated by templates (and I
love it). Their `name` properties [1] should go in .rodata,
right? But why aren't they being put in their own sections
when compiling with -fdata-sections?
[1] -
http
On Wednesday, 14 January 2015 at 08:42:55 UTC, Iain Buclaw via
D.gnu wrote:
On 14 January 2015 at 04:00, Mike via D.gnu
wrote:
On Tuesday, 13 January 2015 at 14:36:15 UTC, Dicebot wrote:
I remember speaking about it with Martin and Daniel during
DConf 2014 and
I think it was Daniel who ment
On 14 January 2015 at 04:00, Mike via D.gnu wrote:
> On Tuesday, 13 January 2015 at 14:36:15 UTC, Dicebot wrote:
>>
>>
>> I remember speaking about it with Martin and Daniel during DConf 2014 and
>> I think it was Daniel who mentioned that by default TypeInfo/ModuleInfo is
>> emitted in some weird
