From: Jonathan Larmour <jifl@eCosCentric.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: Alan Modra <amodra@bigpond.net.au>, binutils@sources.redhat.com
Subject: Re: gc sections and .eh_frame
Date: Fri, 10 Jun 2005 11:49:00 -0000 [thread overview]
Message-ID: <42A97E8C.2040503@eCosCentric.com> (raw)
In-Reply-To: <200506100845.51579.ebotcazou@adacore.com>
Eric Botcazou wrote:
>>I'll be committing a gcc patch soon to fix this on all active gcc branches,
>>pre-approved by David Edelsohn.
>>
>> * config/rs6000/sysv4.h (TARGET_ASM_EXCEPTION_SECTION): Delete.
>
>
> Thanks for tracking this down!
Agreed, thanks! And hopefully that does mean it won't affect other
architectures after all.
But that still leaves us with a huge time gap between now, and when GCC
CVS after the patch finally reaches gcc 4.1.0.
So I would still be keen on pursuing a workaround in binutils, perhaps
along the lines of what I suggested (seeing if .gcc_except_table is in the
input sections), or anything else anyone thinks would work. Adding a
special case for powerpc probably wouldn't be wise as it wouldn't be
appropriate for gcc 4.1.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2005-06-10 11:49 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 [this message]
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=42A97E8C.2040503@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=ebotcazou@adacore.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).