MIURA Masahiro wrote:
Uncomment the line 6, and gdb is now unable to list code:
Please post to bugzilla.
Walter Bright wrote:
Please post to bugzilla.
Done!
http://d.puremagic.com/issues/show_bug.cgi?id=3368
Nick Sabalausky wrote:
Nick Sabalausky a...@a.a wrote in message
news:hadst9$58...@digitalmars.com...
Walter Bright newshou...@digitalmars.com wrote in message
news:hadqcs$30n...@digitalmars.com...
BCS wrote:
Hello Walter,
#ponce wrote:
I think it's disabled in debug mode to keep the
Robert Clipsham wrote:
Leandro Lucarella wrote:
Thanks for finally taking this way, Walter =)
http://www.dsource.org/projects/dmd/timeline
Now that DMD is under version control it should be fairly easy for me to
adapt the automated build system used for ldc for dmd. I can set it up
to
Don wrote:
It's pretty standard, though. For example, there are some bugs which
Visual C++ detects only when the optimiser is on. From memory, they are
all flow-related. The MS docs recommend compiling a release build
occasionally to catch them.
The flow analysis could be run on every
Walter Bright wrote:
Jason House wrote:
With small commits to dmd, it should be trivial to know what small
change in dmd caused a user observable change in behavior.
The problem is, one doesn't know if it is a problem with the change or
if it is a problem with the user code. To determine
Walter Bright wrote:
Don wrote:
It's pretty standard, though. For example, there are some bugs which
Visual C++ detects only when the optimiser is on. From memory, they are
all flow-related. The MS docs recommend compiling a release build
occasionally to catch them.
The flow analysis
Stewart Gordon Wrote:
What is @ going to be used for generally? (What is the essential
difference between an attribute that's an @word and one that's a simple
keyword before or after the type?)
Annotations can be user-defined and can contain data.
Don wrote:
I think that'd be fantastic. It'd be helpful if you could at least get
dstress to run after the main releases. The dstress test page from LDC
doesn't seem to operate any more.
http://www.incasoftware.de/~kamm/ldc/tests/index.html
This page gets updated manually by Christian as he
Walter Bright wrote:
Then please go ahead and set it up.
What exactly would you like setting up? Currently I'm thinking:
* Automated builds of dmd 1 and 2
* Automated builds of druntime, phobos and tango
* Automated DStress runs
* Automated dmd test suite runs (if you're willing to provide me
Lutger wrote:
Walter Bright wrote:
Don wrote:
It's pretty standard, though. For example, there are some bugs which
Visual C++ detects only when the optimiser is on. From memory, they are
all flow-related. The MS docs recommend compiling a release build
occasionally to catch them.
The flow
Robert Clipsham wrote:
Walter Bright wrote:
Then please go ahead and set it up.
What exactly would you like setting up? Currently I'm thinking:
* Automated builds of dmd 1 and 2
* Automated builds of druntime, phobos and tango
* Automated DStress runs
* Automated dmd test suite runs (if
On Tue, Oct 6, 2009 at 3:08 PM, Walter Bright
newshou...@digitalmars.com wrote:
Lutger wrote:
Walter Bright wrote:
Don wrote:
It's pretty standard, though. For example, there are some bugs which
Visual C++ detects only when the optimiser is on. From memory, they are
all flow-related. The
Jarrett Billingsley wrote:
On Tue, Oct 6, 2009 at 3:08 PM, Walter Bright
newshou...@digitalmars.com wrote:
Lutger wrote:
Walter Bright wrote:
Don wrote:
It's pretty standard, though. For example, there are some bugs which
Visual C++ detects only when the optimiser is on. From memory, they
On Wed, 07 Oct 2009 00:54:22 +0400, grauzone n...@example.net wrote:
Jarrett Billingsley wrote:
On Tue, Oct 6, 2009 at 3:08 PM, Walter Bright
newshou...@digitalmars.com wrote:
Lutger wrote:
Walter Bright wrote:
Don wrote:
It's pretty standard, though. For example, there are some bugs
Denis Koroskin wrote:
On Wed, 07 Oct 2009 00:54:22 +0400, grauzone n...@example.net wrote:
Jarrett Billingsley wrote:
On Tue, Oct 6, 2009 at 3:08 PM, Walter Bright
newshou...@digitalmars.com wrote:
Lutger wrote:
Walter Bright wrote:
Don wrote:
It's pretty standard, though. For example,
Walter Bright:
The flow analysis could be run on every compile by default, but it would
make for pretty slow turnaround.
On GCC if you want a safer compilation you add things like -Wall -Wextra, etc.
In D the default is better to be safe (just like you add -release to remove
some safeties),
Walter Bright Wrote:
Jason House wrote:
Which gdb should this release work with?
I seem to have misplaced my patched gdb. The standard gdb 6.8 can show
backtraces but can't list code, even if the code is linked in libraries
from
C++.
If you're using the standard gdb, try
18 matches
Mail list logo
