#855: config/init/defaults.pm: Profiling options are too specific to GCC
-----------------------+----------------------------------------------------
Reporter: jkeenan | Owner:
Type: bug | Status: new
Priority: minor | Milestone:
Component: configure | Version: 1.3.0
Severity: medium | Keywords: profile gcc debug
Lang: | Patch:
Platform: all |
-----------------------+----------------------------------------------------
Comment(by doughera):
Replying to [comment:3 jkeenan]:
> Researching this older ticket, I found the following information for
Solaris and Sun Studio: `-g`
>
> Sources: [http://developers.sun.com/solaris/articles/options.html Sun
Solaris docs] and
[http://developers.sun.com/sunstudio/documentation/techart/gc_options.html
Sun Studio docs]
>
> Can someone verify that these would be appropriate?
It all depends on what you want to do. There are different things one
might do, all of which might be considered "profiling". For Sun Studio
compilers, {{{-g}}} will produce data suitable for analysis with the {{{
analyzer(1) }}} program. {{{-xpg}}} will produce data suitable for {{{
prof }}} or {{{ gprof }}}. {{{ -xprofile={collect|use} }}} will collect
and use data suitable for the compiler itself to use for optimizations,
and {{{-xprofile=tcov}}} will collect data suitable for {{{ tcov(1) }}}.
All of these should be specified both at the compile phase and at the link
phase.
Note too that these flags depend on the compiler, not on the operating
system, so they don't really belong in an operating-system-specific hints
file. (This would also be the case for Intel's compiler.) If
Configure.pl wants to test for them at all, it should be after the
compiler is known.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/855#comment:5>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
