From: Jeff Law <law@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Uros Bizjak <ubizjak@gmail.com>
Subject: Re: [testsuite] PATCH: Add check_effective_target_pie
Date: Mon, 12 Jan 2015 19:59:00 -0000 [thread overview]
Message-ID: <54B42490.40508@redhat.com> (raw)
In-Reply-To: <CAMe9rOqE3xAK6qXOGwf0aecyY5QbARhnsAfOO_Vw8CBXqX9y8w@mail.gmail.com>
On 01/12/15 12:29, H.J. Lu wrote:
>> Is this an inherent restriction of -fPIE, or is it merely an implementation
>> detail? If the latter, is that implementation detail a target issue? ie,
>> could we have a target that supports profiling in conjunction with -fPIE?
>> If so, then this test seems too restrictive.
>
> [hjl@gnu-6 tmp]$ gcc -pie -fPIE -pg h.c
> /usr/local/bin/ld:
> /usr/lib/gcc/x86_64-redhat-linux/4.8.3/../../../../lib64/gcrt1.o:
> relocation R_X86_64_32S against `__libc_csu_fini' can not be used when
> making a shared object; recompile with -fPIC
> /usr/lib/gcc/x86_64-redhat-linux/4.8.3/../../../../lib64/gcrt1.o:
> error adding symbols: Bad value
> collect2: error: ld returned 1 exit status
> [hjl@gnu-6 tmp]$
>
> There is no crt1.o from glibc to support -pg -pie -fPIE.
> I don't know if other targets support -pie -fPIE.
Can you please investigate the questions. Showing me the link failure
doesn't really help much here. It tells me there's no crt1.o, but it
says nothing about *why*.
Is there inherently something about PIE/pg that makes them impossible to
work together or is this an implementation detail? If the latter, then
is the implementation detail a target issue or not.
Jeff
next prev parent reply other threads:[~2015-01-12 19:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 0:25 H.J. Lu
2015-01-12 18:28 ` Jeff Law
2015-01-12 19:58 ` H.J. Lu
2015-01-12 19:59 ` Jeff Law [this message]
[not found] ` <CAMe9rOp1R-FewC1D9fODCe3ia82Ve8YxvfzHPBCaSa9zn4xi+Q@mail.gmail.com>
[not found] ` <54B42880.2040800@redhat.com>
2015-01-12 20:16 ` H.J. Lu
2015-01-12 22:01 ` Magnus Granberg
2015-01-12 22:12 ` Jeff Law
2015-01-13 13:03 ` H.J. Lu
2015-01-13 19:45 ` Jeff Law
2015-02-10 23:11 ` Rainer Orth
2015-02-11 14:04 ` H.J. Lu
2015-02-11 14:11 ` Rainer Orth
2015-02-11 14:20 ` H.J. Lu
2015-02-11 15:19 ` Rainer Orth
2015-02-11 15:45 ` H.J. Lu
2015-02-11 16:16 ` Rainer Orth
2015-02-11 16:45 ` H.J. Lu
2015-01-13 13:04 ` [testsuite] PATCH: Check if -pg available H.J. Lu
2015-01-13 13:15 ` H.J. Lu
2015-01-13 19:49 ` Jeff Law
2015-01-13 20:47 ` H.J. Lu
2015-01-13 21:14 ` Jeff Law
2015-01-13 14:56 ` [testsuite] PATCH: Add check_effective_target_pie H.J. Lu
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=54B42490.40508@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=ubizjak@gmail.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).