From: Konstantin Serebryany <konstantin.s.serebryany@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ian Lance Taylor <iant@google.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Dodji Seketeli <dodji@redhat.com>,
Dmitry Vyukov <dvyukov@google.com>,
Evgeniy Stepanov <eugenis@google.com>
Subject: Re: libsanitizer merge from upstream r175042
Date: Mon, 18 Feb 2013 08:40:00 -0000 [thread overview]
Message-ID: <CAGQ9bdzXkdO=QawM7tMZ8EyVjG9RgGuK69T4qcO4UFBYR3jwaA@mail.gmail.com> (raw)
In-Reply-To: <20130218082056.GY1215@tucnak.zalov.cz>
On Mon, Feb 18, 2013 at 12:20 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Fri, Feb 15, 2013 at 07:39:28AM -0800, Ian Lance Taylor wrote:
>> On Thu, Feb 14, 2013 at 11:45 PM, Konstantin Serebryany
>> <konstantin.s.serebryany@gmail.com> wrote:
>> >
>> > Unfortunately, the test does not work if gold is the system linker.
>> > Any suggestion on how to make the test work with either linker?
>>
>> I don't know of a way to set the address of the text segment for both
>> GNU ld and gold. As you have observed, GNU ld's -Ttext-segment option
>> is the same as gold's -Ttext option. GNU ld's -Ttext option is
>> useless on ELF systems.
>>
>> I will add -Ttext-segment to gold as an alias for -Ttext, but that
>> won't help you today.
>
> Can't you use then something like:
> // RUN: %clangxx_asan -m64 -DBUILD_SO=1 -fPIC -shared %s -o %t.so -Wl,-Ttext-segment=0x3600000000 || %clangxx_asan -m64 -DBUILD_SO=1 -fPIC -shared %s -o %t.so -Wl,-Ttext=0x3600000000 || exit 0
Yep, that's what I was going to do once Ian confirmed that -Ttext in
gold is equivalent to Ttext-segment bfd ld.
http://llvm.org/viewvc/llvm-project?rev=175431&view=rev
Thanks!
--kcc
>
> ?
>
> Jakub
next prev parent reply other threads:[~2013-02-18 8:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 9:20 Konstantin Serebryany
2013-02-13 9:51 ` Jakub Jelinek
2013-02-13 10:28 ` Konstantin Serebryany
2013-02-13 10:32 ` Jakub Jelinek
2013-02-13 11:59 ` Jakub Jelinek
2013-02-13 12:33 ` Konstantin Serebryany
2013-02-13 12:48 ` Jakub Jelinek
2013-02-13 12:58 ` Konstantin Serebryany
2013-02-13 13:07 ` Jakub Jelinek
2013-02-13 13:28 ` Richard Biener
2013-02-13 13:33 ` Jakub Jelinek
2013-02-13 13:39 ` Konstantin Serebryany
2013-02-13 15:19 ` Jakub Jelinek
2013-02-13 16:48 ` Jack Howarth
2013-02-13 20:12 ` Jakub Jelinek
2013-02-14 8:48 ` Jakub Jelinek
2013-02-14 11:56 ` Konstantin Serebryany
2013-02-14 12:19 ` Jakub Jelinek
2013-02-14 12:56 ` Konstantin Serebryany
2013-02-15 7:45 ` Konstantin Serebryany
2013-02-15 8:26 ` Jakub Jelinek
2013-02-15 8:48 ` Konstantin Serebryany
2013-02-15 9:06 ` Jakub Jelinek
2013-02-15 9:30 ` Konstantin Serebryany
2013-02-15 9:37 ` Jakub Jelinek
2013-02-15 9:47 ` Konstantin Serebryany
2013-02-15 12:02 ` Konstantin Serebryany
2013-02-22 16:32 ` Jakub Jelinek
2013-02-28 12:30 ` Konstantin Serebryany
2013-02-28 19:56 ` Jakub Jelinek
2013-02-15 15:39 ` Ian Lance Taylor
2013-02-18 8:21 ` Jakub Jelinek
2013-02-18 8:40 ` Konstantin Serebryany [this message]
2013-02-13 14:46 ` Jack Howarth
2013-02-13 18:29 ` H.J. Lu
2013-02-14 8:08 ` Konstantin Serebryany
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='CAGQ9bdzXkdO=QawM7tMZ8EyVjG9RgGuK69T4qcO4UFBYR3jwaA@mail.gmail.com' \
--to=konstantin.s.serebryany@gmail.com \
--cc=dodji@redhat.com \
--cc=dvyukov@google.com \
--cc=eugenis@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=jakub@redhat.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).