From: Andreas Schwab <schwab@linux-m68k.org>
To: Jim Wilson <jimw@sifive.com>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/2] gcc/riscv: Add a mechanism to remove some calls to _riscv_save_0
Date: Sat, 31 Aug 2019 13:12:00 -0000 [thread overview]
Message-ID: <87d0gldb02.fsf@hase.home> (raw)
In-Reply-To: <CAFyWVaYbTsONTL3d_u-BVQ71tMmsDYgXDfp6nyw9GaQb-iAPpw@mail.gmail.com> (Jim Wilson's message of "Fri, 30 Aug 2019 17:09:57 -0700")
On Aug 30 2019, Jim Wilson <jimw@sifive.com> wrote:
> produced shared libraries that failed again, which turned out because
> the save/restore functions use the alternate link register t0/x5 which
> is clobbered by plts, so we can't call them in shared libraries at
> all.
Shouldn't the save/restore functions always be local to the object, thus
never be called through the PLT?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2019-08-31 7:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 19:31 [PATCH 0/2] RISCV: Reduce code size when compiling with -msave-restore Andrew Burgess
2019-08-19 19:47 ` [PATCH 2/2] gcc/riscv: Add a mechanism to remove some calls to _riscv_save_0 Andrew Burgess
2019-08-23 7:46 ` Jim Wilson
2019-08-26 2:17 ` Jim Wilson
2019-08-31 2:55 ` Jim Wilson
2019-08-31 13:12 ` Andreas Schwab [this message]
2019-08-31 13:57 ` Andreas Schwab
2019-09-06 23:41 ` Jim Wilson
2019-08-24 17:18 ` Jim Wilson
2019-10-21 12:53 ` Andrew Burgess
2019-10-23 0:59 ` Jim Wilson
2019-10-28 17:18 ` Andrew Burgess
2019-08-19 19:50 ` [PATCH 1/2] gcc/riscv: Include more registers in SIBCALL_REGS Andrew Burgess
2019-08-19 19:54 ` Andrew Waterman
2019-08-23 7:13 ` Jim Wilson
2019-08-24 10:55 ` Jim Wilson
2019-10-16 21:14 ` [PATCH] RISC-V: " Jim Wilson
2019-10-17 14:15 ` Andrew Burgess
2019-10-17 22:05 ` Jim Wilson
2019-10-17 22:22 ` Andrew Burgess
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=87d0gldb02.fsf@hase.home \
--to=schwab@linux-m68k.org \
--cc=andrew.burgess@embecosm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimw@sifive.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).