This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: When to emit C++ debug info?
Daniel Berlin <dberlin@dberlin.org> writes:
| On Jan 5, 2004, at 3:05 PM, Gabriel Dos Reis wrote:
|
| > Daniel Berlin <dberlin@dberlin.org> writes:
| >
| > | I'll simply note that compilers which provide fast compile-link-debug
| > | cycles (MSVC for instance) usually use some kind of separated debug
| > | info to do this (and eliminate as they compile), and *not*
| > heuristics.
| > |
| > | But since nobody seems to agree, i'll simply go away.
| >
| > Well, I support separate debug info; I consider emitting everyting in
| > the .o file a non-starter. If that makes you go away, that is sade.
|
| I consider emitting everything in a .o to be a non-starter too, more
| or less.
| But I *also* consider trying to come up with magical heuristics that
| arguably don't even work in the common case, to be a non-starter.
| >
| Maybe we should be exploring *why* everyone else use separated debug
| info, and not heuristics, before claiming the heuristics are a good
| idea.
OK. I'm in total agreement.
-- Gaby