public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [build] Fix Solaris 2/x86 GD/LD TLS code sequences with Sun ld
Date: Tue, 24 May 2011 17:41:00 -0000	[thread overview]
Message-ID: <yddaaecrqx6.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <BANLkTimCbqEEZoUqVuTDp7iWav0GGiat9Q@mail.gmail.com> (Uros	Bizjak's message of "Tue, 24 May 2011 18:35:13 +0200")

Uros Bizjak <ubizjak@gmail.com> writes:

>> Assembler: eh_globals.cc
>>        "/var/tmp//ccJ1MA8h.s", line 17 : Syntax error
>>        Near line: "    call    __tls_get_addr(%rip)@plt"
>>        "/var/tmp//ccJ1MA8h.s", line 38 : Syntax error
>>        Near line: "    call    __tls_get_addr(%rip)@plt"
>> make[9]: *** [eh_globals.lo] Error 1
>
> Bah. %P has a special handling that removes (%rip). Are you sure Sun
> assembler requests @plt in PIC and non-PIC cases? Can we solve this

Pretty much so: my first attempts to resolve this consisted in taking
the regular gcc assembler output and mangling it until it worked with ld.

> with TARGET_SUN_TLS somehow?

We could certainly duplicate (some of) the logic that %P already uses,
but I though it easier to just introduce a straightforward variant (%p)
instead.  It's not pretty, but it worked.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2011-05-24 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 20:04 Rainer Orth
2011-05-23 21:32 ` Uros Bizjak
2011-05-24 16:42   ` Rainer Orth
2011-05-24 16:43     ` Uros Bizjak
2011-05-24 17:19       ` Rainer Orth
2011-05-24 17:40         ` Uros Bizjak
2011-05-24 17:41           ` Rainer Orth [this message]
2011-05-24 18:07             ` Uros Bizjak
2011-05-26 11:12               ` Rainer Orth
2011-05-27  0:47                 ` Uros Bizjak
2011-05-27 13:35                   ` Rainer Orth
2011-05-27 14:00                     ` Uros Bizjak
2011-05-27 16:57                       ` Rainer Orth
2011-05-24 17:40         ` Joseph S. Myers

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=yddaaecrqx6.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gcc-patches@gcc.gnu.org \
    --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).