public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: sergiodj@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] archer-sergiodj-stap: Commenting BFD specific code. Date: Mon, 28 Mar 2011 23:25:00 -0000 [thread overview] Message-ID: <20110328232553.24423.qmail@sourceware.org> (raw) The branch, archer-sergiodj-stap has been updated via 2e9812415849a1216e5b42f189ace5946b2c5bcb (commit) from 39408dcdff87543c04dccce5e9f586607a974c14 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit 2e9812415849a1216e5b42f189ace5946b2c5bcb Author: Sergio Durigan Junior <sergiodj@redhat.com> Date: Mon Mar 28 20:25:45 2011 -0300 Commenting BFD specific code. ----------------------------------------------------------------------- Summary of changes: bfd/elf-bfd.h | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) First 500 lines of diff: diff --git a/bfd/elf-bfd.h b/bfd/elf-bfd.h index 50c1272..d50823a 100644 --- a/bfd/elf-bfd.h +++ b/bfd/elf-bfd.h @@ -1476,6 +1476,8 @@ enum Tag_compatibility = 32 }; +/* The following struct stores information about every SystemTap section + found in the object file. */ struct sdt_note { struct sdt_note *next; @@ -1640,6 +1642,9 @@ struct elf_obj_tdata bfd_size_type build_id_size; bfd_byte *build_id; + /* Linked-list containing information about every Systemtap section + found in the object file. Each section corresponds to one entry + in the list. */ struct sdt_note *sdt_note_head; /* True if the bfd contains symbols that have the STT_GNU_IFUNC hooks/post-receive -- Repository for Project Archer.
reply other threads:[~2011-03-28 23:25 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110328232553.24423.qmail@sourceware.org \ --to=sergiodj@sourceware.org \ --cc=archer-commits@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: linkBe 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).