public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: binutils@sources.redhat.com, Jonathan Larmour <jifl@ecoscentric.com>
Subject: Re: gc sections and .eh_frame
Date: Tue, 28 Jun 2005 02:58:00 -0000	[thread overview]
Message-ID: <20050628025830.GA8706@bubble.grove.modra.org> (raw)
In-Reply-To: <200506271355.49260.ebotcazou@adacore.com>

On Mon, Jun 27, 2005 at 01:55:49PM +0200, Eric Botcazou wrote:
> > None of the proposed solutions is right.  If you take a look at a
> > typical .eh_frame, you'll see relocs pointing at text sections and
> > .gcc_except_table (or .rodata for broken ppc compilers).  Changing
> > garbage collection to process .rela.eh_frame thus runs into the problem
> > of distinguishing the two types of reloc:  You need to ignore the
> > former, and mark sections for the latter.
> 
> That's exactly what I proposed in my last message, but I suggested passing a 

Sorry, I was just going by memory.

> parameter to _bfd_elf_gc_mark to make it "forget" code sections.  It seems 
> autodetecting .eh_frame is more straightforward.
> 
> > Try the following totally untested patch.
> >
> > 	* elflink.c (_bfd_elf_gc_mark): Handle .eh_frame relocs specially..
> > 	(bfd_elf_gc_sections): ..rather than totally ignoring .eh_frame.
> > 	Don't recheck sections we have already marked.
> 
> I think it doesn't work (alone) either, because you unconditionally mark 
> all .gcc_except_table* sections, which themselves point to the functions.

That doesn't make any difference, because .gcc_except_table* is marked
via KEEP() in the linker script.  So I don't think you need anything
more than the patch I posted.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

  reply	other threads:[~2005-06-28  2:58 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 17:48 Jonathan Larmour
2005-06-07 18:00 ` Eric Botcazou
2005-06-07 18:11   ` Jonathan Larmour
2005-06-08  2:09 ` Alan Modra
2005-06-08 11:13   ` Jonathan Larmour
2005-06-08 19:10     ` Richard Henderson
2005-06-08 19:29       ` Jonathan Larmour
2005-06-08 19:32         ` Richard Henderson
2005-06-08 21:36           ` Jonathan Larmour
2005-06-08 22:02             ` Richard Henderson
2005-06-09 10:33               ` Jonathan Larmour
2005-06-09 11:38                 ` Eric Botcazou
2005-06-09 12:07                   ` Jonathan Larmour
2005-06-09 12:49                     ` Alan Modra
2005-06-09 13:02                     ` Eric Botcazou
2005-06-09 13:50                       ` Jonathan Larmour
2005-06-09 14:22                         ` Eric Botcazou
2005-06-09 14:33                           ` Jonathan Larmour
2005-06-10  4:23                             ` Alan Modra
2005-06-10  6:46                               ` Eric Botcazou
2005-06-10 11:49                                 ` Jonathan Larmour
2005-06-10 11:55                             ` Eric Botcazou
2005-06-10 12:09                               ` Alan Modra
2005-06-10 12:51                                 ` Jonathan Larmour
2005-06-10 13:44                                   ` Eric Botcazou
2005-06-10 14:26                                     ` Jonathan Larmour
2005-06-10 14:50                                       ` Eric Botcazou
2005-06-10 14:58                                         ` Jonathan Larmour
2005-06-10 15:13                                           ` Eric Botcazou
2005-06-22 11:46                                         ` Jonathan Larmour
2005-06-25 17:28                                           ` Alan Modra
2005-06-27 11:56                                             ` Eric Botcazou
2005-06-28  2:58                                               ` Alan Modra [this message]
2005-06-28  7:40                                                 ` Eric Botcazou
2005-06-28 11:42                                                   ` Alan Modra
2005-06-28 11:58                                                     ` Eric Botcazou
2005-06-29  1:24                                                       ` Alan Modra
2005-06-29  6:52                                                         ` Eric Botcazou
2005-06-29 12:45                                                           ` Jonathan Larmour
2005-06-29 13:54                                                         ` Alan Modra
2005-06-29 22:31                                                           ` Jonathan Larmour
2005-06-30 22:28                                                             ` Alan Modra
2005-07-01 13:31                                                               ` Jonathan Larmour
2005-07-04  4:50                                                                 ` Alan Modra
2005-07-04 10:55                                                                   ` Jonathan Larmour
2005-07-26 11:30                                                           ` Alan Modra
2005-07-26 12:05                                                             ` Alan Modra
2005-08-25  0:06                                                             ` Jim Blandy
2005-08-25  0:48                                                               ` Alan Modra
2005-06-10 13:35                                 ` Eric Botcazou

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=20050628025830.GA8706@bubble.grove.modra.org \
    --to=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=ebotcazou@adacore.com \
    --cc=jifl@ecoscentric.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).