#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 doughera):
Replying to [comment:8 jkeenan]:
> Is there any meaningful distinction between the `profile` configuration
option handled in `init::defaults` and the `debugging` option handled in
`inter::progs`? Couldn't we collapse the two into each other? And if we
do so, which should be the name of the option: 'profile' or 'debugging'?
I would favor collapsing the two into "debugging", even though they are
logically distinct. There are very many different things one might
imagine asking a compiler to do; it doesn't make sense to make up separate
Configure.pl ones for each. Ultimately, as long as there is some way to
pass arbitrary options to the compiler through Configure.pl, people will
be able to do whatever it is they are trying to do.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/855#comment:9>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
