public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug ld/12851] --gc-sections doesn't work on note sections
Date: Tue, 14 Jun 2011 02:46:00 -0000	[thread overview]
Message-ID: <bug-12851-6586-tovotxAGxy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12851-6586@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12851

--- Comment #12 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> 2011-06-14 02:45:16 UTC ---
CVSROOT:    /cvs/src
Module name:    src
Changes by:    amodra@sourceware.org    2011-06-14 02:45:12

Modified files:
    bfd            : ChangeLog elflink.c elf-bfd.h elfxx-target.h 
                     elf32-arm.c elf32-tic6x.c 

Log message:
    PR ld/12851
    * elflink.c (_bfd_elf_gc_mark_extra_sections): New function.
    (elf_gc_sweep): Don't treat debug and sections like .comment
    specially here.
    (bfd_elf_gc_sections): Treat note sections as gc roots only when
    not part of a group.  Always call gc_mark_extra_sections.
    * elf-bfd.h (_bfd_elf_gc_mark_extra_sections): Declare.
    * elfxx-target.h (elf_backend_gc_mark_extra_sections): Default to
    _bfd_elf_gc_mark_extra_sections.
    * elf32-arm.c (elf32_arm_gc_mark_extra_sections): Call
    _bfd_elf_gc_mark_extra_sections.
    * elf32-tic6x.c (elf32_tic6x_gc_mark_extra_sections): Likewise.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/ChangeLog.diff?cvsroot=src&r1=1.5384&r2=1.5385
http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/elflink.c.diff?cvsroot=src&r1=1.410&r2=1.411
http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/elf-bfd.h.diff?cvsroot=src&r1=1.321&r2=1.322
http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/elfxx-target.h.diff?cvsroot=src&r1=1.125&r2=1.126
http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/elf32-arm.c.diff?cvsroot=src&r1=1.270&r2=1.271
http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/elf32-tic6x.c.diff?cvsroot=src&r1=1.25&r2=1.26

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-06-14  2:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  3:15 [Bug uprobes/12851] New: Wrong section group usage in <sys/sdt.h> hjl.tools at gmail dot com
2011-06-07 11:33 ` [Bug uprobes/12851] " mjw at redhat dot com
2011-06-07 13:11 ` hjl.tools at gmail dot com
2011-06-07 13:59 ` mjw at redhat dot com
2011-06-07 14:42 ` hjl.tools at gmail dot com
2011-06-08 15:16 ` mjw at redhat dot com
2011-06-08 15:44 ` hjl.tools at gmail dot com
2011-06-08 15:44 ` hjl.tools at gmail dot com
2011-06-08 17:39 ` [Bug ld/12851] " hjl.tools at gmail dot com
2011-06-08 17:40 ` [Bug ld/12851] --gc-sections doesn't work on comdat sections hjl.tools at gmail dot com
2011-06-08 20:09 ` [Bug ld/12851] --gc-sections doesn't work on note sections hjl.tools at gmail dot com
2011-06-08 20:11 ` hjl.tools at gmail dot com
2011-06-09  4:53 ` cvs-commit at gcc dot gnu.org
2011-06-09 12:43 ` hjl.tools at gmail dot com
2011-06-14  2:46 ` cvs-commit at gcc dot gnu.org [this message]
2011-06-14  2:48 ` cvs-commit at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-12851-6586-tovotxAGxy@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).