public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Matt Thomas <matt@3am-software.com>
To: Alex Matveev <alex.matveev@samsung.com>
Cc: binutils@sourceware.org
Subject: Re: ARM position-independent code in Gas
Date: Thu, 27 Feb 2014 03:45:00 -0000	[thread overview]
Message-ID: <5C8C7404-1588-4109-9DF1-AF18F448524D@3am-software.com> (raw)
In-Reply-To: <20140227000201.42c81571@amatveev>


On Feb 26, 2014, at 12:02 PM, Alex Matveev <alex.matveev@samsung.com> wrote:

> Hello all,
> 
> I'm working on a project which is part C and part assembler (ARM, GCC
> 4.8.2, binutils 2.23.1), and final binary should be
> position-independent.
> 
> I compile stuff with -fpie and link with -pie -fpie. This works out
> fine on the C side - I get R_ARM_RELATIVE and R_ARM_ABS32 relocations,
> fix'em up on startup, all good. But the problem is, there are no relocs
> from assembler objects, thus the result is not PIC. Trying to trick Gas
> into producing relocs, I've found couple of
> not-very-extensively-documented directives - '.reloc' and ARM-specific
> '.word foo(RELOC)', but I haven't had any success with them either.
> 
> Can GAS in principle produce PIC? Or am I missing something obvious?

gas doesn't know PIC.  The arm assembly has to be PIC to start.

> And a side question: I'm somewhat puzzled by the presence of
> R_ARM_ABS32 relocations in the final output - aren't they static
> (AAELF says so)?

They are static.

Not sure which processor you are using but you can do PIC like:

	movw	r0, #:lower16:foo-.LPIC0
	movt	r0, #:upper16:foo-.LPIC0
	add	r0, r0, pc
	nop	@ at this point r0 points at foo and you can replace foo
		@ by another instruction the same size as the add.
.LPIC0:


You can also do symbol relative:

bar:	@ function entry
	adr	ip, bar
	movw	r0, #:lower16:foo-bar
	movt	r0, #:upper16:foo-bar
	add	r0, r0, ip

If you are dealing with shared libraries and global data:

	ldr	r3, .Lgot
	add	r3, r3, pc
	ldr	r0, .Lfoo	@ load got slot offset
.LPIC0:	ldr	r0, [r0, r3]
	...
.Lgot:
	.long	_GLOBAL_OFFSET_TABLE_-.LPIC0
.Lfoo:
	.word	foo(GOT)	@ reserves a slot in the GOT for foo

using -S -c -fPIC on c source and looking at the assembly produced
can prove to be instructive.

      reply	other threads:[~2014-02-27  3:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 20:02 Alex Matveev
2014-02-27  3:45 ` Matt Thomas [this message]

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=5C8C7404-1588-4109-9DF1-AF18F448524D@3am-software.com \
    --to=matt@3am-software.com \
    --cc=alex.matveev@samsung.com \
    --cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).