public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Andy Lutomirski <luto@amacapital.net>
Cc: Borislav Petkov <bp@alien8.de>, Jan Beulich <JBeulich@suse.com>,
	Binutils <binutils@sourceware.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Avoiding unnecessary jump relocations in gas?
Date: Mon, 18 May 2015 13:06:00 -0700	[thread overview]
Message-ID: <555A4628.4060802@zytor.com> (raw)
In-Reply-To: <CAMe9rOqrdRUH9kPU6aO=fmtfdPoua319kvsZgRovEyT37kencQ@mail.gmail.com>

On 05/18/2015 01:02 PM, H.J. Lu wrote:
>>
>> I wonder if it would make sense to have explicit mnemonics for the
>> one-byte offset and four-byte offset jump variants.  Sometimes users
>> want a jump with a 32-bit offset for reasons that have nothing to do
>> with link-time or load-time relocations.
>>
> 
> There is:
> 
> jmp.d32 foo
> 

How far back does that syntax work?

	-hpa



  reply	other threads:[~2015-05-18 20:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07  6:02 Avoiding unnecessary jump relocations in gas? Andy Lutomirski
2015-05-07 11:52 ` Jan Beulich
2015-05-07 16:21   ` H.J. Lu
2015-05-08  3:22     ` Andy Lutomirski
2015-05-08 12:09       ` H.J. Lu
2015-05-08 20:16         ` H.J. Lu
2015-05-18 19:36           ` Andy Lutomirski
2015-05-18 20:01             ` H. Peter Anvin
2015-05-18 20:11               ` Borislav Petkov
2015-05-18 20:02             ` H.J. Lu
2015-05-18 20:06               ` H. Peter Anvin [this message]
2015-05-18 20:25                 ` H.J. Lu
2015-05-18 20:28                   ` H. Peter Anvin
2015-05-18 20:34                     ` H. Peter Anvin
2015-05-20 20:53                       ` Andy Lutomirski
2015-05-20 20:59                         ` H. Peter Anvin
2015-05-20 21:47                           ` Andy Lutomirski
2015-05-20 21:58                             ` H. Peter Anvin
2015-05-20 22:08                             ` H. Peter Anvin
2015-05-20 22:17                               ` Andy Lutomirski
2015-05-20 22:21                                 ` H. Peter Anvin

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=555A4628.4060802@zytor.com \
    --to=hpa@zytor.com \
    --cc=JBeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=bp@alien8.de \
    --cc=hjl.tools@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    /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