From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fw@deneb.enyo.de>,
Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH] linux: mips: Fix getdents64 fallback on mips64-n32
Date: Tue, 17 Nov 2020 15:08:56 -0300 [thread overview]
Message-ID: <c50da5ca-421c-e8e6-9d38-070ff2cc6d06@linaro.org> (raw)
In-Reply-To: <877dqj6fe2.fsf@mid.deneb.enyo.de>
On 17/11/2020 14:51, Florian Weimer wrote:
> * Adhemerval Zanella via Libc-alpha:
>
>> Not that good, I see a large stack usage (1456 vs 1152 from my initial
>> version) and some more memory load/store memory instructions. The
>> kdp type change does not change the code generation.
>
> That's why I suggested to use two separately defined struct types for
> this.
>
How different than my second attempt [1] is your suggestion? I tried
to follow your description on this one.
[1] https://sourceware.org/pipermail/libc-alpha/2020-November/119688.html
next prev parent reply other threads:[~2020-11-17 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 21:17 [PATCH] linux: mips: Fix getdents64 fallback on mips64-n32 Adhemerval Zanella via Libc-alpha
2020-11-16 21:22 ` Florian Weimer
2020-11-17 13:19 ` Adhemerval Zanella via Libc-alpha
2020-11-17 13:38 ` Andreas Schwab
2020-11-17 17:37 ` Adhemerval Zanella via Libc-alpha
2020-11-17 17:51 ` Florian Weimer
2020-11-17 18:08 ` Adhemerval Zanella via Libc-alpha [this message]
2021-01-22 12:49 ` Florian Weimer via Libc-alpha
2021-01-22 14:20 ` Adhemerval Zanella via Libc-alpha
2021-01-22 16:02 ` Florian Weimer via Libc-alpha
2020-11-16 21:40 ` Andreas Schwab
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c50da5ca-421c-e8e6-9d38-070ff2cc6d06@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fw@deneb.enyo.de \
--cc=schwab@linux-m68k.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 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).