From: Andy Lutomirski <luto@MIT.EDU>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
Ingo Molnar <mingo@elte.hu>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@MIT.EDU>
Subject: [PATCH resend 0/2] Fix x86-64 linker script when using gold
Date: Sat, 23 Jul 2011 15:19:01 -0400 [thread overview]
Message-ID: <cover.1311448660.git.luto@mit.edu> (raw)
In-Reply-To: <201107231559.23537.a.miskiewicz@gmail.com>
[resent because I misspelled linux-kernel the first time.]
We were hitting two bugs:
http://sourceware.org/bugzilla/show_bug.cgi?id=13019
http://sourceware.org/bugzilla/show_bug.cgi?id=13023
The former was really a bug on the linker script that neither the
old bfd linker nor the kernel loader cared about. It caused gold to
bail, though.
The second is, I think, a legitimate bug in gold. But rather than
regressing on current gold versions, we can work around it.
This is what I get for messing with the linker script :-/
Andy Lutomirski (2):
x86-64: Move the "user" vsyscall segment out of the data segment.
x86-64: Work around gold bug 13023
arch/x86/kernel/vmlinux.lds.S | 46 ++++++++++++++++++++++------------------
1 files changed, 25 insertions(+), 21 deletions(-)
--
1.7.6
next prev parent reply other threads:[~2011-07-23 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 13:59 3.1 git: ld: error: dot may not move backward Arkadiusz Miskiewicz
2011-07-23 14:18 ` Markus Trippelsdorf
2011-07-23 19:19 ` Andy Lutomirski [this message]
2011-07-23 19:19 ` [PATCH resend 1/2] x86-64: Move the "user" vsyscall segment out of the data segment Andy Lutomirski
2011-07-23 19:19 ` [PATCH resend 2/2] x86-64: Work around gold bug 13023 Andy Lutomirski
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=cover.1311448660.git.luto@mit.edu \
--to=luto@mit.edu \
--cc=a.miskiewicz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.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