This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [build, driver] RFC: Support compressed debug sections
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- Cc: <gcc-patches at gcc dot gnu dot org>, Paolo Bonzini <bonzini at gnu dot org>
- Date: Sun, 5 May 2013 14:15:28 +0000
- Subject: Re: [build, driver] RFC: Support compressed debug sections
- References: <yddvc7tmhx9 dot fsf at lokon dot CeBiTec dot Uni-Bielefeld dot DE> <Pine dot LNX dot 4 dot 64 dot 1304261553200 dot 27966 at digraph dot polyomino dot org dot uk> <yddd2tcazm5 dot fsf at lokon dot CeBiTec dot Uni-Bielefeld dot DE> <Pine dot LNX dot 4 dot 64 dot 1305032000020 dot 30366 at digraph dot polyomino dot org dot uk> <yddfvy2l9xa dot fsf at CeBiTec dot Uni-Bielefeld dot DE>
I still have no idea from your answer how a user is meant to know whether
to use the option when compiling, linking or both, which is what needs to
be clear from invoke.texi.
What does it mean for the option to be supported for compiling but not
linking? What in that case will the linker do with compressed debug
sections on input? Combine them in some way, good or bad? Uncompress
them?
Likewise, for it to be supported for linking but not compiling? Will the
linker then compress the uncompressed sections it receives on input?
I think it would be better if the option semantics are more like "if you
pass the same option when both compiling and linking, the linked output
will have the sections appropriately compressed as specified by the
option, whether or not the individual .o files do" - and if this can't be
supported with the tools being used, don't allow the option.
--
Joseph S. Myers
joseph@codesourcery.com