All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@redhat.com>
To: Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>
Cc: linux-mips@linux-mips.org
Subject: Re: Unmatched R_MIPS_HI16/R_MIPS_LO16 on gcc 3.5
Date: Tue, 24 May 2005 07:56:35 +0100	[thread overview]
Message-ID: <87acml863g.fsf@firetop.home> (raw)
In-Reply-To: <Pine.GSO.4.10.10505240837530.12717-100000@helios.et.put.poznan.pl> (Stanislaw Skowronek's message of "Tue, 24 May 2005 08:39:14 +0200 (MET DST)")

Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL> writes:

>> It should generate:
>> 
>>     R_MIPS_HI16
>>     R_MIPS_HI16
>>     R_MIPS_LO16
>> 
>> And yes, the idea that several HI16s can be associated with the same
>> LO16 is also a GNU extension. ;)
>
> Good, no problem - thanks for confirming my darkest suspicions. How can I
> detect this? (I've got to emit SGI-compliant ECOFF.) I can emit sham
> relocs into .rel.text that point into specially added synthetic
> instructions.

Sorry if this is a dumb question, but why do you need to generate
_relocatable_ ECOFF?  If you really need to do that, I think you'll
just have to force gcc to use assembler macros, ala:

   gcc -mno-explicit-relocs -mno-split-addresses

Richard

  reply	other threads:[~2005-05-24  6:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23  7:10 Unmatched R_MIPS_HI16/R_MIPS_LO16 on gcc 3.5 Stanislaw Skowronek
2005-05-23 11:17 ` Richard Sandiford
2005-05-23 16:19   ` Stanislaw Skowronek
2005-05-23 17:23     ` Richard Sandiford
2005-05-23 17:32       ` Stanislaw Skowronek
2005-05-24  6:35         ` Richard Sandiford
2005-05-24  6:39           ` Stanislaw Skowronek
2005-05-24  6:56             ` Richard Sandiford [this message]
2005-05-24  6:58               ` Stanislaw Skowronek
2005-05-24 10:40                 ` Maciej W. Rozycki
2005-05-24 10:47                   ` Stanislaw Skowronek
2005-05-24 11:40                     ` Maciej W. Rozycki
2005-05-24 10:50                   ` Richard Sandiford
2005-05-24 14:22                   ` Ralf Baechle
2005-05-24 14:50                     ` Maciej W. Rozycki
2005-05-24 15:00                       ` Ralf Baechle
2005-05-24 15:04                         ` Maciej W. Rozycki

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=87acml863g.fsf@firetop.home \
    --to=rsandifo@redhat.com \
    --cc=linux-mips@linux-mips.org \
    --cc=sskowron@ET.PUT.Poznan.PL \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.