#855: config/init/defaults.pm: Profiling options are too specific to GCC
-----------------------+----------------------------------------------------
Reporter: jkeenan | Owner: jkeenan
Type: bug | Status: assigned
Priority: minor | Milestone:
Component: configure | Version: 1.3.0
Severity: medium | Keywords: profile gcc debug
Lang: | Patch:
Platform: all |
-----------------------+----------------------------------------------------
Comment(by darbelo):
Replying to [comment:13 jkeenan]:
> Follow-up question:
>
> If a user has requested an optimized build, does it make any sense to
have values for `link_debug` and `ld_debug`? In the optimize case,
shouldn't they be set to empty strings just like `cc_debug`?
The answer to that depends on wether you consider building an optimized
parrot should exclude the possibility of building a debug-able parrot.
While it's true that the configure system has no direct provisions for
this, it is (or used to be, I haven't tried in som time) relatively simple
to build an optimized parrot with debugging symbols. IIRC chromatic used
to do this regularly so that he could get line number information out of
gdb when debugging optimized builds, it's likely we should take this use
case into consideration when evaluating the impact of changes to the debug
flags in optimized builds.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/855#comment:14>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
