From: Paolo Bonzini <pbonzini@redhat.com>
To: Ed Maste <emaste@freebsd.org>
Cc: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Could configure generate QEMU's linker scripts?
Date: Sun, 19 May 2013 21:24:41 +0200 [thread overview]
Message-ID: <519926F9.30503@redhat.com> (raw)
In-Reply-To: <CAPyFy2AD87vdosCw0fzDroL-PyoFLfOQewVQiWeRvOEmfHy7uQ@mail.gmail.com>
Il 19/05/2013 18:30, Ed Maste ha scritto:
> I'd rather
> not end up just introducing a parallel set of ldscript files for
> FreeBSD, so would like to generate it from the default built-in one if
> possible.
>
> For the FreeBSD x86-64 case I can create a suitable linker script (at
> least, one identical to what's in the FreeBSD ports tree) with just
> the following:
>
> ld --verbose | sed \
> -e '1,/==================================================/d' \
> -e '/==================================================/,$d' \
> -e 's/0x400000/0x60000000/g'
>
> That is, it just changes the start address. Is this generally the
> only difference between QEMU's linker scripts and system built-ins?
> (Perhaps we're missing other changes in FreeBSD, or platforms other
> than x86_64 have more extensive changes?)
Is this still needed if you compile QEMU with PIE? Currently we do that
only for a few architectures due to lack of testing, but it could well
be made the default, and help dropping the linker scripts.
Paolo
next prev parent reply other threads:[~2013-05-19 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 16:30 [Qemu-devel] Could configure generate QEMU's linker scripts? Ed Maste
2013-05-19 19:24 ` Paolo Bonzini [this message]
2013-05-20 0:22 ` Aurelien Jarno
2013-05-20 17:21 ` Richard Henderson
2013-05-21 17:51 ` Ed Maste
2013-05-21 18:14 ` Richard Henderson
2013-06-02 17:15 ` Peter Maydell
2013-06-03 14:23 ` Richard Henderson
2013-06-03 14:57 ` Peter Maydell
2013-06-03 15:01 ` Richard Henderson
2013-06-04 15:55 ` Claudio Fontana
2013-06-04 16:13 ` Peter Maydell
2013-06-04 16:18 ` Richard Henderson
2013-06-05 9:03 ` Claudio Fontana
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=519926F9.30503@redhat.com \
--to=pbonzini@redhat.com \
--cc=emaste@freebsd.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.