From: John David Anglin <dave.anglin@bell.net>
To: Masahiro Yamada <masahiroy@kernel.org>,
linux-parisc@vger.kernel.org, Helge Deller <deller@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH] linux/export: fix reference to exported functions for parisc64
Date: Tue, 5 Sep 2023 18:14:33 -0400 [thread overview]
Message-ID: <122c0f7d-8f76-0f88-e12e-90a50478ec38@bell.net> (raw)
In-Reply-To: <20230905190828.790400-1-masahiroy@kernel.org>
On 2023-09-05 3:08 p.m., Masahiro Yamada wrote:
> I checked the assembler output, and noticed function references are
> prefixed with P%, so the situation in parisc64 is similar to ia64.
Function references are prefixed with P% when they occur in data like the following:
.dword P%func
This causes the generation of a function descriptor. The assembler and linker can't handle the P%
prefix in other situations.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2023-09-05 22:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 19:08 [PATCH] linux/export: fix reference to exported functions for parisc64 Masahiro Yamada
2023-09-05 21:57 ` John David Anglin
2023-09-05 23:59 ` John David Anglin
2023-09-07 22:02 ` John David Anglin
2023-09-09 17:20 ` Masahiro Yamada
2023-09-09 19:20 ` Masahiro Yamada
2023-09-10 7:47 ` Masahiro Yamada
2023-09-10 21:30 ` John David Anglin
2023-09-12 13:01 ` Helge Deller
2023-09-12 13:20 ` John David Anglin
2023-09-12 14:05 ` Helge Deller
2023-09-12 14:53 ` John David Anglin
2023-09-12 21:53 ` John David Anglin
2023-09-13 17:58 ` John David Anglin
2023-09-13 21:22 ` John David Anglin
2023-09-13 23:45 ` Damien Le Moal
2023-09-14 0:29 ` John David Anglin
2023-09-14 0:45 ` Damien Le Moal
2023-09-14 1:15 ` Damien Le Moal
2023-09-14 2:24 ` Damien Le Moal
2023-09-14 15:07 ` John David Anglin
2023-09-14 21:59 ` Damien Le Moal
2023-09-05 22:14 ` John David Anglin [this message]
[not found] ` <1MbRk3-1q6Cp42Bcv-00bwDk@mail.gmx.net>
2023-09-09 17:15 ` Masahiro Yamada
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=122c0f7d-8f76-0f88-e12e-90a50478ec38@bell.net \
--to=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.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