From: Ed Maste <emaste@freebsd.org>
To: qemu-devel@nongnu.org
Cc: Ed Maste <emaste@freebsd.org>
Subject: [Qemu-devel] [RFT PATCH v2] configure: Simplify alternate .text segment
Date: Thu, 20 Jun 2013 09:15:43 -0400 [thread overview]
Message-ID: <1371734143-780-1-git-send-email-emaste@freebsd.org> (raw)
For bsd-user and linux-user emulation modes QEMU needs to be linked at an
alternate .text segment address, so that it's out of the way of the guest
executable. Instead of including modified linker scripts for each arch,
just set the address with -Ttext-segment if supported, or by using sed to
edit the default linker script.
Note that ldscripts/alpha.ld was already unused prior to this change, as
it was handled by the "default placement of the application is fine" case.
Signed-off-by: Ed Maste <emaste@freebsd.org>
---
Changes from v1:
- Drop removal of ldscripts from the patch for now. They remain unused
with v2 and can be removed later, but this makes the patch smaller
during review and testing.
- Don't require knowledge of the default .text address, as suggested by
Richard Henderson.
- Use configure's existing compile_prog to test for acceptance of the
linker flag rather than a hack that fails on current binutils versions.
configure | 37 +++++---
diff --git a/configure b/configure
index ad32f87..b3025df 100755
--- a/configure
+++ b/configure
@@ -4072,9 +4072,6 @@ if test "$gcov" = "yes" ; then
echo "GCOV=$gcov_tool" >> $config_host_mak
fi
-# generate list of library paths for linker script
-$ld --verbose -v 2> /dev/null | grep SEARCH_DIR > config-host.ld
-
# use included Linux headers
if test "$linux" = "yes" ; then
mkdir -p linux-headers
@@ -4437,21 +4434,35 @@ if test "$gprof" = "yes" ; then
fi
fi
-if test "$ARCH" = "tci"; then
- linker_script=""
-else
- linker_script="-Wl,-T../config-host.ld -Wl,-T,\$(SRC_PATH)/ldscripts/\$(ARCH).ld"
-fi
-
if test "$target_linux_user" = "yes" -o "$target_bsd_user" = "yes" ; then
+ textseg_addr=
case "$ARCH" in
- alpha | s390x | aarch64)
- # The default placement of the application is fine.
+ arm | hppa | i386 | ia64 | m68k | ppc | ppc64 | s390 | sparc | sparc64 | x86_64)
+ textseg_addr=0x60000000
;;
- *)
- ldflags="$linker_script $ldflags"
+ mips)
+ textseg_addr=0x400000
;;
esac
+ if [ -n "$textseg_addr" ]; then
+cat > $TMPC <<EOF
+int main(void) { return 0; }
+EOF
+ try_ldflags="-Ttext-segment=$textseg_addr"
+ if compile_prog "" "$try_ldflags"; then
+ ldflags="$ldflags $try_ldflags"
+ else
+ # In case ld does not support -Ttext-segment, edit the default linker
+ # script via sed to set the .text start addr. This is needed on FreeBSD
+ # at least.
+ $ld --verbose | sed \
+ -e '1,/==================================================/d' \
+ -e '/==================================================/,$d' \
+ -e "s/[.] = [0-9a-fx]* [+] SIZEOF_HEADERS/. = $textseg_addr + SIZEOF_HEADERS/" \
+ -e "s/__executable_start = [0-9a-fx]*/__executable_start = $textseg_addr/" > config-host.ld
+ ldflags="$ldflags -Wl,-T../config-host.ld"
+ fi
+ fi
fi
echo "LDFLAGS+=$ldflags" >> $config_target_mak
next reply other threads:[~2013-06-20 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 13:15 Ed Maste [this message]
2013-06-21 18:37 ` [Qemu-devel] [RFT PATCH v2] configure: Simplify alternate .text segment 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=1371734143-780-1-git-send-email-emaste@freebsd.org \
--to=emaste@freebsd.org \
--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 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 NNTP newsgroup(s).