From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: "Florian Weimer" <fweimer@redhat.com>,
"Michal Suchánek" <msuchanek@suse.de>
Cc: linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org,
"Lynn A. Boger" <laboger@linux.ibm.com>
Subject: Re: PIE binaries are no longer mapped below 4 GiB on ppc64le
Date: Wed, 31 Oct 2018 18:23:37 -0300 [thread overview]
Message-ID: <87efc5n73a.fsf@linux.ibm.com> (raw)
In-Reply-To: <877ehyf1cj.fsf@oldenburg.str.redhat.com>
Florian Weimer <fweimer@redhat.com> writes:
> * Michal Suchánek:
>
>> On Wed, 31 Oct 2018 18:20:56 +0100
>> Florian Weimer <fweimer@redhat.com> wrote:
>>
>>> And it needs to be built with:
>>>
>>> go build -ldflags=-extldflags=-pie extld.go
>>>
>>> I'm not entirely sure what to make of this, but I'm worried that this
>>> could be a regression that matters to userspace.
>>
>> I encountered the same when trying to build go on ppc64le. I am not
>> familiar with the internals so I just let it be.
>>
>> It does not seem to matter to any other userspace.
>
> It would matter to C code which returns the address of a global variable
> in the main program through and (implicit) int return value.
I wonder if this is restricted to linker that Golang uses.
Were you able to reproduce the same problem with Binutils' linker?
--
Tulio Magno
next prev parent reply other threads:[~2018-10-31 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 17:20 Florian Weimer
2018-10-31 17:50 ` Michal Suchánek
2018-10-31 17:54 ` Florian Weimer
2018-10-31 21:23 ` Tulio Magno Quites Machado Filho [this message]
2018-10-31 21:28 ` Florian Weimer
2018-10-31 22:04 ` Tulio Magno Quites Machado Filho
2018-10-31 22:41 ` Michal Suchánek
2018-10-31 22:24 ` Benjamin Herrenschmidt
2018-11-02 4:38 ` Nick Piggin
2018-11-01 3:55 ` Michael Ellerman
2018-11-01 6:49 ` Alan Modra
2018-11-02 9:41 ` Michael Ellerman
2018-11-01 11:20 ` Florian Weimer
2018-11-02 9:37 ` Michael Ellerman
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=87efc5n73a.fsf@linux.ibm.com \
--to=tuliom@ascii.art.br \
--cc=fweimer@redhat.com \
--cc=laboger@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
/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