From: Simon Burge <simonb@wasabisystems.com>
To: Richard Henderson <rth@redhat.com>
Cc: Nick Clifton <nickc@redhat.com>, Jakub Jelinek <jakub@redhat.com>,
Simon Burge <simonb@wasabisystems.com>,
Ian Lance Taylor <ian@airs.com>,
binutils@sources.redhat.com
Subject: Re: .eh_frame section on alpha
Date: Tue, 04 Jan 2005 21:27:00 -0000 [thread overview]
Message-ID: <20050104212720.GA23945@thoreau.thistledown.com.au> (raw)
In-Reply-To: <20050104175111.GG3605@redhat.com>
On Tue, Jan 04, 2005 at 09:51:11AM -0800, Richard Henderson wrote:
> On Tue, Jan 04, 2005 at 10:14:03AM +0000, Nick Clifton wrote:
> > Presumably yes. But I assume that the feeling is that invoking an
> > assembler switch is simpler for the user than requiring them to write or
> > edit linker scripts.
>
> If you're writing boot loaders, you're already writing linker scripts.
We currently don't use a linker script. Here's the complete linker
line:
alpha--netbsd-ld -Ttext 0x20000000 -N -e start -o bootxx_ffs.sym \
start.o bootxx.o booted_dev.o blkdev.o prom.o prom_disp.o putstr.o \
panic_putstr.o lib/sa/libsa.a kern/libkern.a -Map bootxx_ffs.map
Since we don't already use (and therefore have to maintain) a separate
linker script, a command line option to not generate these new .eh_frame
sections seems like the cleanest solution to me.
Cheers,
Simon.
--
Simon Burge <simonb@wasabisystems.com>
NetBSD Development, Support and Service: http://www.wasabisystems.com/
next prev parent reply other threads:[~2005-01-04 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 13:22 Simon Burge
2004-12-24 15:00 ` Ian Lance Taylor
2004-12-29 7:39 ` Simon Burge
2005-01-04 9:36 ` Nick Clifton
2005-01-04 9:58 ` Jakub Jelinek
2005-01-04 10:06 ` Nick Clifton
2005-01-04 17:51 ` Richard Henderson
2005-01-04 21:27 ` Simon Burge [this message]
2005-01-04 22:40 ` Jakub Jelinek
2005-01-05 2:17 ` Simon Burge
2005-01-05 3:14 ` Richard Henderson
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=20050104212720.GA23945@thoreau.thistledown.com.au \
--to=simonb@wasabisystems.com \
--cc=binutils@sources.redhat.com \
--cc=ian@airs.com \
--cc=jakub@redhat.com \
--cc=nickc@redhat.com \
--cc=rth@redhat.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).