From: Eric Botcazou <ebotcazou@adacore.com>
To: Jonathan Larmour <jifl@ecoscentric.com>
Cc: binutils@sources.redhat.com
Subject: Re: gc sections and .eh_frame
Date: Thu, 09 Jun 2005 13:02:00 -0000 [thread overview]
Message-ID: <200506091501.34783.ebotcazou@adacore.com> (raw)
In-Reply-To: <42A8311E.5090402@eCosCentric.com>
> Can I ask where the used .gcc_except_table.* sections _are_ meant to be
> marked? I cannot see anywhere that _bfd_elf_discard_section_eh_frame does
> it, for example.
The (patched) compiler will mark them.
> Why would .gcc_except_table.* get marked, but .rodata not get marked for
> powerpc?
Clearly .rodata needs to be explicitly KEEPed for your powerpc target, the
same way .gcc_except_table has been marked as KEEP for generic ELF.
> Separately, I still consider it an issue to break existing linker scripts
> (and the failure mode is very obscure and difficult to track down when you
> encounter it, I can tell you!).
The alternative is a useless -function-sections --gc-sections with DWARF-2 EH.
--
Eric Botcazou
next prev parent reply other threads:[~2005-06-09 13:02 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 [this message]
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
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=200506091501.34783.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=binutils@sources.redhat.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).