Bill Baxter:
That's a good point. I never think of stuff like that because I use
dsss most of the time.
You want per-file flags? Ha! Dsss laughs at you. Unfortunately. :-(
I usually compile programs with bud, that applies the same thing to all
modules. I presume as dsss.
As soon as Walter
On Fri, 16 Jan 2009 21:18:46 +1300, bearophile bearophileh...@lycos.com
wrote:
Bill Baxter:
That's a good point. I never think of stuff like that because I use
dsss most of the time.
You want per-file flags? Ha! Dsss laughs at you. Unfortunately. :-(
I usually compile programs with
Hello dsimcha,
I'm working on optimizing some code now, and a nagging issue that I've
been meaning to bring up is how slow stuff runs when profiling is
turned on. It seems that, given any code that's slow enough to be
worth profiling/optimizing, the DMD profiler slows it down further, to
the
bearophile wrote:
Bill Baxter:
That's a good point. I never think of stuff like that because I
use dsss most of the time. You want per-file flags? Ha! Dsss
laughs at you. Unfortunately. :-(
I usually compile programs with bud, that applies the same thing to
all modules. I presume as dsss.
Reply to bearophile,
Bill Baxter:
That's a good point. I never think of stuff like that because I use
dsss most of the time.
You want per-file flags? Ha! Dsss laughs at you. Unfortunately.
:-(
I usually compile programs with bud, that applies the same thing to
all modules. I presume as
Reply to Denis,
On Fri, 16 Jan 2009 22:47:26 +0300, BCS a...@pathlink.com wrote:
A better way to go could be to have a config file passed to DMD that
has a long list of codefile.d: -flags and let DMD pick the correct
flags to append to the command line
You can't set version (and some
dsimcha wrote:
I'm working on optimizing some code now, and a nagging issue that I've been
meaning to bring up is how slow stuff runs when profiling is turned on. It
seems that, given any code that's slow enough to be worth
profiling/optimizing, the DMD profiler slows it down further, to the
Tom S schrieb:
You could try using an external non-intrusive profiler. If you compile
your stuff with GCC on *nix, I've been hearing that kcachegrind is
pretty awesome: http://kcachegrind.sourceforge.net/html/Home.html
If you'd like to profile a DMD-Win-compiled executable, I've written a
I'm working on optimizing some code now, and a nagging issue that I've been
meaning to bring up is how slow stuff runs when profiling is turned on. It
seems that, given any code that's slow enough to be worth
profiling/optimizing, the DMD profiler slows it down further, to the point
where it's
Nick Sabalausky:
Isn't that kind of a common thing with profilers in general?
Any physical measure alters the thing to be measured, but with a good enough
brain you can generally invent ways to decrease such alteration to tolerable
levels. So it's a matter of inventing better solutions.
There
bearophile wrote:
Nick Sabalausky:
Isn't that kind of a common thing with profilers in general?
Any physical measure alters the thing to be measured, but with a good enough
brain you can generally invent ways to decrease such alteration to tolerable
levels. So it's a matter of inventing
On Fri, Jan 16, 2009 at 9:44 AM, Christopher Wright dhase...@gmail.com wrote:
bearophile wrote:
Nick Sabalausky:
Isn't that kind of a common thing with profilers in general?
Any physical measure alters the thing to be measured, but with a good
enough brain you can generally invent ways to
Bill Baxter wrote:
Right, that would probably do the trick, except I don't think there's
anyway to programatically turn D's profiler on or off. So if you've
got a program with a big startup cost and you want to profile
something that happens after startup, it means you could be waiting a
long
13 matches
Mail list logo
