All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Maybe another or1k bug
Date: Sun, 11 Jul 2021 10:36:32 +0200	[thread overview]
Message-ID: <D68EB4FF-538F-4FF1-ACFC-24AFEB098314@benettiengineering.com> (raw)
In-Reply-To: <YOdxwtNeQ2eUr+L3@antec>

Hi Stafford, All,

> Il giorno 8 lug 2021, alle ore 23:44, Stafford Horne <shorne@gmail.com> ha scritto:
> 
> On Wed, Jul 07, 2021 at 02:25:39PM -0700, Richard Henderson wrote:
>>> On 7/7/21 2:06 PM, Stafford Horne wrote:
>>> +CC Richards other account
>>> 
>>> Hi Richard,
>>> 
>>> I Cced this to you twiddle.net account you on this one originally. Do you recall
>>> why we added the below check in or1k bfd?  It seems to be overly restrictive and
>>> causing some issues below.
>>> 
>>>  case R_OR1K_INSN_REL_26:
>>>    if (bfd_link_pic (info) && !SYMBOL_REFERENCES_LOCAL (info, h))
>>>      ERROR
>> ...
>>>> 4. The symbols are from `readelf -s`:
>>>> 
>>>>    221: 00008ce4   716 FUNC    GLOBAL PROTECTED   24 alSourcePausev
>>>>    222: 00008fb0    36 FUNC    GLOBAL PROTECTED   24 alSourcePause
>>>>    223: 00008fd4   784 FUNC    GLOBAL PROTECTED   24 alSourceStopv
>>>>    224: 000092e4    36 FUNC    GLOBAL PROTECTED   24 alSourceStop
>>>>    225: 00009308   720 FUNC    GLOBAL PROTECTED   24 alSourceRewindv
>>>>    226: 000095d8    36 FUNC    GLOBAL PROTECTED   24 alSourceRewind
>> 
>> Ah, STV_PROTECTED.  Unusual.
>> 
>> It looks like this should be SYMBOL_CALLS_LOCAL.  The only difference from
>> SYMBOL_REFERENCES_LOCAL is versus protected symbols.
> 
> Thanks Richard.
> 
> I will post a patch for this in a few days.  Or, maybe Giulio can do it if he
> has time.

Substituting SYMBOL_REFERENCES_LOCAL with SYMBOL_CALLS_LOCAL fixes the problem.
Only one thing, is it valid for every case in that switch or must it be only for R_OR1K_INSN_REL_26?

I’ve built and entire buildroot system with all cases with that new condition and it builds successfully.

Please let me know so I can send a patch for this.

Thank you and
Best regards
Giulio Benetti

  parent reply	other threads:[~2021-07-11  8:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dbcce22d-b288-2451-4a8d-681f802c6f49@benettiengineering.com>
2021-05-24 22:34 ` [OpenRISC] Maybe another or1k bug Stafford Horne
2021-05-24 23:03   ` Giulio Benetti
2021-06-17 23:41     ` Stafford Horne
2021-07-07 21:06       ` Stafford Horne
2021-07-07 21:25         ` Richard Henderson
2021-07-08 21:44           ` Stafford Horne
2021-07-08 22:57             ` Giulio Benetti
2021-07-11  8:36             ` Giulio Benetti [this message]
2021-07-11 13:24               ` Richard Henderson
2021-07-11 13:41                 ` Giulio Benetti

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=D68EB4FF-538F-4FF1-ACFC-24AFEB098314@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=openrisc@lists.librecores.org \
    /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.