From: Nick Clifton <nickc@redhat.com>
To: Jan Beulich <JBeulich@novell.com>,
Daniel Jacobowitz <dan@codesourcery.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] x86_64: push <symoffs> creates wrong relocation
Date: Mon, 04 Apr 2005 10:13:00 -0000 [thread overview]
Message-ID: <42511298.1040105@redhat.com> (raw)
In-Reply-To: <s24d7def.036@emea1-mh.id2.novell.com>
Hi Jan,
> Now, should any of them (clearly not the .macro one) also go into 2.16? Thanks, Jan
This is up to Daniel,
I think that these two would be reasonable:
2005-04-01 Jan Beulich <jbeulich@novell.com>
* i386-dis.c (PNI_Fixup): Neither mwait nor monitor have any
visible operands in Intel mode. The first operand of monitor is
%rax in 64-bit mode.
2005-04-01 Jan Beulich <jbeulich@novell.com>
* i386-dis.c (INVLPG_Fixup): Decode rdtscp; change code to allow for
easier future additions.
Cheers
Nick
next parent reply other threads:[~2005-04-04 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s24d7def.036@emea1-mh.id2.novell.com>
2005-04-04 10:13 ` Nick Clifton [this message]
2005-04-04 13:23 ` Daniel Jacobowitz
2005-04-01 15:59 Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2005-04-01 14:35 Nick Clifton
2005-02-28 16:04 Jan Beulich
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=42511298.1040105@redhat.com \
--to=nickc@redhat.com \
--cc=JBeulich@novell.com \
--cc=binutils@sources.redhat.com \
--cc=dan@codesourcery.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).