From: Nick Clifton <nickc@redhat.com>
To: ford@vss.fsi.com
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] Support DWARF 2/3 on i?86 PE
Date: Thu, 29 Apr 2004 16:07:00 -0000 [thread overview]
Message-ID: <m3brlavkny.fsf@redhat.com> (raw)
Hi Brian,
Sorry for the long delay in approving this patch. I have however now
looked at it, approved it and applied it to the sources.
Cheers
Nick
> bfd/ChangeLog:
> 2004-04-14 Brian Ford <ford@vss.fsi.com>
>
> * bfd.c (bfd_get_sign_extend_vma): Add pe[i]-i386 case to DJGPP hack.
> * coffcode.h (DOT_DEBUG, GNU_LINKONCE_WI): Define.
> [!COFF_WITH_PE] (sec_to_styp_flags, styp_to_sec_flags): Use them.
> (coff_compute_section_file_positions) [RS6000COFF_C]: Likewise.
> [COFF_WITH_PE] (sec_to_styp_flags): Handle DWARF 2/3 .debug* and
> .gnu.linkonce.wi. sections.
> * pe-i386.c (COFF_SUPPORT_GNU_LINKONCE): Define.
> (COFF_SECTION_ALIGNMENT_ENTRIES): Add entries for .debug and
> .gnu.linkonce.wi..
> * pei-i386.c (COFF_SUPPORT_GNU_LINKONCE): Likewise.
> (COFF_SECTION_ALIGNMENT_ENTRIES): Likewise.
>
> gas/ChangeLog:
> 2004-04-14 Brian Ford <ford@vss.fsi.com>
>
> * dwarf2dbg.c (dwarf2_finish): Add SEC_DEBUGGING to section flags.
>
> ld/ChangeLog:
> 2004-04-14 Brian Ford <ford@vss.fsi.com>
>
> * scripttempl/pe.sc: Handle .debug* and .gnu.linkonce.wi.* sections
> for DWARF 2/3. Update stab section's syntax.
Approved.
next reply other threads:[~2004-04-29 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 16:07 Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-16 3:36 Brian Ford
[not found] ` <20040416033107.GD2557@bubble.modra.org>
2004-04-16 4:14 ` Brian Ford
2004-04-16 4:22 ` Alan Modra
2004-04-16 15:29 ` Brian Ford
2004-04-17 11:29 ` Alan Modra
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=m3brlavkny.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=ford@vss.fsi.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).