[Issue 13726] Build Phobos and Druntime with stack frames enabled (-gs) (page 2)

https://issues.dlang.org/show_bug.cgi?id=13726 --- Comment #11 from Martin Nowak <code@dawg.eu> --- (In reply to Vladimir Panteleev from comment #9) > I don't understand... I'm not sure what the scheme is on POSIX, but on Win32, exception frames and stack frames are completely separate (they form two distinct linked lists which do not overlap). > https://gnu.wildebeest.org/blog/mjw/2007/08/23/stack-unwinding/ --

November 29, 2014

[Issue 13726] Build Phobos and Druntime with stack frames enabled (-gs)

Posted by Martin Nowak

Permalink

Martin Nowak

Permalink

https://issues.dlang.org/show_bug.cgi?id=13726

--- Comment #12 from Martin Nowak <code@dawg.eu> ---
(In reply to Vladimir Panteleev from comment #6)
> Martin, do you have a benchmark for which the performance difference is non-negligible?

It would affect any leaf function that is not inlined.
For example this would kill what Manu had in mind for std.simd, a module where
each function consists of a few SIMD instrustions.

> I've been building D from source code on my server for a while now, just to enable stack frames. They are invaluable for debugging, I use them for production all the time. I am confident that at the moment, D will benefit more from stack frames in Phobos/Druntime than 0.1% in performance.

It's 0.1% performance loss for you but maybe 1 or 2% for someone else.
There is so much we can do to improve stack traces, but enforcing stack frames
is a performance trade-off.

--

https://issues.dlang.org/show_bug.cgi?id=13726 --- Comment #13 from Vladimir Panteleev <thecybershadow@gmail.com> --- (In reply to Martin Nowak from comment #12) > There is so much we can do to improve stack traces, but enforcing stack frames is a performance trade-off. On Windows, breakpointing onInvalidMemoryOperationError does not result in a readable stack trace when using Visual Studio with neither Win32, Win32+cv2pdb, or Win64. This means that we are not emitting debug information that can replace stack frames for either CV or PDB formats. --

https://issues.dlang.org/show_bug.cgi?id=13726 --- Comment #14 from Vladimir Panteleev <thecybershadow@gmail.com> --- (In reply to Vladimir Panteleev from comment #0) > An example use case where stack frames are useful is debugging InvalidMemoryOperation errors. Right now, there are TWO threads in the front page of digitalmars.D.learn asking about this error. Nobody can give good advice on reliably determining what exactly causes it. I'm writing a wiki page with a guide on how to use Digger to rebuild D so you can get a good stack trace, but right now the situation is miserable. --

https://issues.dlang.org/show_bug.cgi?id=13726 Sobirari Muhomori <dfj1esp02@sneakemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http://forum.dlang.org/thre | |ad/ossuvfmqthllgdpgzntm@for | |um.dlang.org --

https://issues.dlang.org/show_bug.cgi?id=13726 --- Comment #15 from Sobirari Muhomori <dfj1esp02@sneakemail.com> --- (In reply to Walter Bright from comment #2) > Every bit of performance matters. D is constantly being compared for speed with other tools. > > Building phobos for maximum debugging support is completely at odds with performance. Not for debugging, but for decent newbie user experience. --

https://issues.dlang.org/show_bug.cgi?id=13726 Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://issues.dlang.org/sh | |ow_bug.cgi?id=8841 --

Forums