[Bug gold/14265] -gc-sections ignores KEEP annotations
http://sourceware.org/bugzilla/show_bug.cgi?id=14265 Nick Clifton nickc at redhat dot com changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1 from Nick Clifton nickc at redhat dot com 2012-08-09 07:39:49 UTC --- Hi Ian, I have been looking at this PR, trying to find a way to solve it, but I am hopelessly lost. So I am asking for some guidance... It seems to me that gold parses the KEEP directives and stores them in Output_section_element_input class, but then it just ignores them. Then when Sized_relobj_file runs garbage collection there appears to be no way to connect the Output_section pointer to the input sections that contributed to it. So I guess my question is - when garbage collection occurs, how do I find out if a particular input section should be KEPT ? Cheers Nick -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug gold/14265] -gc-sections ignores KEEP annotations
http://sourceware.org/bugzilla/show_bug.cgi?id=14265 --- Comment #2 from Ian Lance Taylor ian at airs dot com 2012-08-09 15:00:36 UTC --- The key point connecting the Output_section_element_input and the Layout code is the call to Output_section_element_input::match_name. From the Layout side, it's the call to ss-output_section_name in Layout::chose_output_section. So I would suggest having Output_section_element_input::match_name return whether the section is kept (e.g., in a new bool* parameter). Then the Layout code can pass that information back from Layout::layout, and Sized_relobj_file::do_layout can add the input section to the worklist. Thanks for looking at this. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/14444] objdump fails on .ko with -gdwarf-4
http://sourceware.org/bugzilla/show_bug.cgi?id=1 --- Comment #3 from Lluís Batlle viriketo at gmail dot com 2012-08-09 17:30:47 UTC --- All my kernel modules have that trouble. I only run 'make' for the modules in the linux kernel, with gcc 4.6.3, with DEBUG_INFO enabled, and this patch: --- a/Makefile +++ b/Makefile @@ -593,8 +593,8 @@ endif endif ifdef CONFIG_DEBUG_INFO -KBUILD_CFLAGS += -g -KBUILD_AFLAGS += -gdwarf-2 +KBUILD_CFLAGS += -gdwarf-4 -fvar-tracking-assignments +KBUILD_AFLAGS += -gdwarf-4 endif ifdef CONFIG_DEBUG_INFO_REDUCED -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/14444] objdump fails on .ko with -gdwarf-4
http://sourceware.org/bugzilla/show_bug.cgi?id=1 --- Comment #4 from H.J. Lu hjl.tools at gmail dot com 2012-08-09 19:16:04 UTC --- (In reply to comment #3) All my kernel modules have that trouble. I only run 'make' for the modules in the linux kernel, with gcc 4.6.3, with It works fine with the Linux binutils 2.23.51.0.1 and GCC 4.7. Which binutils did you use to build kernel modules? -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
