public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	Binutils <binutils@sourceware.org>,
	       Alan Modra <amodra@gmail.com>
Subject: Re: [patch ld bfd gas]: Handle linkonce for cfi generated debug_frame and eh_frame data
Date: Tue, 26 Apr 2011 15:29:00 -0000	[thread overview]
Message-ID: <4DB6E500.5030807@redhat.com> (raw)
In-Reply-To: <BANLkTim3DpFxpY+yjuGExYWPZXRE3xwvag@mail.gmail.com>

Hi Kai,

>> ChangeLog bfd/
>> >  2011-04-18  Kai Tietz
>> >
>> >          * coffcode.h (sec_to_styp_flags): Allow linkonce for
>> >          debugging sections.
>> >
>> >  ChangeLog gas/
>> >  2011-04-18  Kai Tietz
>> >
>> >         * dw2gencfi.c (dwcfi_seg_list): New struct.
>> >         (dwcfi_hash): New static hash variable.
>> >         (get_debugseg_name): New.
>> >         (alloc_debugseg_item): New.
>> >         (make_debug_seg): New.
>> >         (dwcfi_hash_insert): New.
>> >         (dwcfi_hash_find): New.
>> >         (dwcfi_hash_find_or_make): New.
>> >         (cfi_insn_data): New member cur_seg.
>> >         (cie_entry): Likewise.
>> >         (fde_entry): New cseg and handled members.
>> >         (alloc_fde_entry): Initialize cseg member.
>> >         (alloc_cfi_insn_data): Initialize cur_seg member.
>> >         (dot_cfi_sections): Compare for beginning of
>> >         section names via strncmp.
>> >         (get_cfi_seg): New.
>> >         (cfi_finish): Treat link-once sections.
>> >         (is_now_linkonce_segment): New local helper.
>> >         (output_cie): Ignore cie entries not member of current
>> >         segment.
>> >         (output_fde): Likewise.
>> >         (select_cie_for_fde): Likewise.
>> >         (cfi_change_reg_numbers): Add new argument for current segment
>> >         and ignore insn elements, if not part of current segment.
>> >         * ehopt.c (get_cie_info): Use strncmp for
>> >         section name matching.
>> >         (heck_eh_frame): Likewise.
>> >
>> >  ChangeLog ld/
>> >
>> >  2011-04-18  Kai Tietz
>> >
>> >         * scripttempl/pe.sc: Likewise.
>> >         * scripttempl/pep.sc: Likewise.
>> >
>> >  ChangeLog ld/testsuite/
>> >
>> >  2011-04-18  Kai Tietz
>> >
>> >          * ld-pe/pe.exp: Add cfi/cfi32 tests.
>> >          * ld-pe/cfi.d: New.
>> >          * ld-pe/cfi32.d: New.
>> >          * ld-pe/cfia.s: New.
>> >          * ld-pe/cfib.s: New.
>> >

Approved and applied,  Sorry for the delay.

Cheers
   Nick

  reply	other threads:[~2011-04-26 15:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18  9:34 Kai Tietz
2011-04-18 12:43 ` H.J. Lu
2011-04-18 20:04   ` Kai Tietz
2011-04-24 10:20     ` Kai Tietz
2011-04-26 15:29       ` Nick Clifton [this message]
2011-04-27 20:35         ` gas -Werror compilation break [Re: [patch ld bfd gas]: Handle linkonce for cfi generated debug_frame and eh_frame data] Jan Kratochvil
2011-05-05  0:29           ` Dave Korn
2011-05-05  8:45             ` Alan Modra
2011-05-05 13:21               ` Alan Modra
2011-05-06 17:58                 ` Dave Korn
2011-05-07  2:53                   ` Alan Modra
2011-05-05  8:50             ` Kai Tietz

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=4DB6E500.5030807@redhat.com \
    --to=nickc@redhat.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=ktietz70@googlemail.com \
    /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).