I wasn't trying to be pompous! It's just our project name, but I
thought fission to be quite appropriate for what it does. How does
-gsplit or -gsplit-dwarf work for you?
Or -gsplit-debug?
-g is already supposed to convey the debug, so I think that -gsplit-dwarf is
the best proposal (and
For google/gcc-4_6 branch. (To be submitted for trunk soon.)
The option name sounds like the brainchild of the marketing department. :-)
Can we avoid going nuclear in the compiler and use something more mundane?
--
Eric Botcazou
On 13/03/12 04:14 , Eric Botcazou wrote:
For google/gcc-4_6 branch. (To be submitted for trunk soon.)
The option name sounds like the brainchild of the marketing department. :-)
Can we avoid going nuclear in the compiler and use something more mundane?
I, for one, welcome our new nuclear
I, for one, welcome our new nuclear overlords.
AFAICS the internal switch is called dwarf_split_debug_info so a short moniker
based on it would be more understandable (and avoid a useless pomposity).
--
Eric Botcazou
I, for one, welcome our new nuclear overlords.
AFAICS the internal switch is called dwarf_split_debug_info so a short moniker
based on it would be more understandable (and avoid a useless pomposity).
I wasn't trying to be pompous! It's just our project name, but I
thought fission to be quite
On Tue, Mar 13, 2012 at 11:56 AM, Cary Coutant ccout...@google.com wrote:
I, for one, welcome our new nuclear overlords.
AFAICS the internal switch is called dwarf_split_debug_info so a short
moniker
based on it would be more understandable (and avoid a useless pomposity).
I wasn't trying
On 13/03/12 15:43 , Xinliang David Li wrote:
On Tue, Mar 13, 2012 at 11:56 AM, Cary Coutantccout...@google.com wrote:
I, for one, welcome our new nuclear overlords.
AFAICS the internal switch is called dwarf_split_debug_info so a short moniker
based on it would be more understandable (and
Add GCC support for -gfission option. Debug info is partitioned
into skeleton sections that will remain in the .o file, and dwo
sections that will be moved to a .dwo file. After compilation,
the gcc driver calls objcopy twice: once to extract the dwo
sections into the .dwo file, and a second
[Revised patch to fix problem with ASM_FINAL_SPEC in the case where
neither -c nor -o are specified.]
Add GCC support for -gfission option. Debug info is partitioned
into skeleton sections that will remain in the .o file, and dwo
sections that will be moved to a .dwo file. After compilation,
