On Fri, Feb 27, 2015 at 8:37 AM, Lynn A. Boger
wrote:
> At a minimum I think it should be mentioned in libgo/README.
(Where "it" means that libgo should not be stripped.)
I've committed this minor update to libgo/README.
Ian
diff -r b0d3b9400c63 libgo/README
--- a/libgo/README Thu Mar 12 1
libgo sizes
32665042: original size
27607770: after removing the debug sections using the objcopy command
from below
22474602: after removing all debug sections using objcopy
On 03/02/2015 02:08 PM, Ian Lance Taylor wrote:
On Mon, Mar 2, 2015 at 12:05 PM, Lynn A. Boger
wrote:
I removed
I removed the 3 debug sections from libgo that were listed on the
objcopy command.
I left in: debug_info, debug_line, debug_abbrev, debug_ranges, and
debug_str in their original form.
On 03/02/2015 01:58 PM, Ian Lance Taylor wrote:
On Mon, Mar 2, 2015 at 11:50 AM, Lynn A. Boger
wrote:
obj
On Mon, Mar 2, 2015 at 12:05 PM, Lynn A. Boger
wrote:
> I removed the 3 debug sections from libgo that were listed on the objcopy
> command.
>
> I left in: debug_info, debug_line, debug_abbrev, debug_ranges, and
> debug_str in their original form.
Understood. I mean: if you add up the total siz
On Mon, Mar 2, 2015 at 11:50 AM, Lynn A. Boger
wrote:
>
> objcopy -R .debug_aranges -R .debug_frame -R .debug_loc libgo.so.7.0.0
What percentage of the total size of .debug sections got removed by
this process?
A problem with that approach is that .debug_info and .debug_abbrevs
sections are larg
On 02/27/2015 02:46 PM, Ian Lance Taylor wrote:
On Fri, Feb 27, 2015 at 12:07 PM, Matthias Klose wrote:
is there anything which could be stripped without scarifying functionality?
Linux distributions usually strip things by default, so a hint what exactly is
needed to keep the functionality wo
On Fri, Feb 27, 2015 at 12:07 PM, Matthias Klose wrote:
>
> is there anything which could be stripped without scarifying functionality?
> Linux distributions usually strip things by default, so a hint what exactly is
> needed to keep the functionality would be appreciated.
What is needed is file/
On 02/27/2015 04:59 PM, Ian Lance Taylor wrote:
> On Fri, Feb 27, 2015 at 7:21 AM, wrote:
>>
>> As discussed in this bugzilla, the debug info from libgo should not be
>> stripped or some things won't work as documented, like runtime.Callers. Is
>> that information documented anywhere so that anyo
At a minimum I think it should be mentioned in libgo/README.
I'll have to ask around to find out where would be best so that anyone
who builds libgo for distribution knows that the debug info should not
be stripped.
I'm not sure about other places
On 02/27/2015 09:59 AM, Ian Lance Taylor wrot
On Fri, Feb 27, 2015 at 7:21 AM, wrote:
>
> As discussed in this bugzilla, the debug info from libgo should not be
> stripped or some things won't work as documented, like runtime.Callers. Is
> that information documented anywhere so that anyone who builds gccgo and
> libgo and provides it to oth
This patch to the gccgo manual clarifies that you should not strip Go
programs, as requested by PR 63565. I also added a note about using
cgo to interoperate between Go and C. Bootstrapped on
x86_64-unknown-linux-gnu. Committed to mainline.
Ian
2015-01-23 Ian Lance Taylor
PR go/63565
* gc
11 matches
Mail list logo
