public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Monday Patch Queue Review pdate (2024-04-01)
Date: Mon, 15 Apr 2024 16:19:31 +0100	[thread overview]
Message-ID: <Zh1FgzAu8ZMKH-7v@antec> (raw)
In-Reply-To: <663ff605-1893-4df4-8fa8-e919bac845c3@linaro.org>

On Mon, Apr 01, 2024 at 11:00:59AM -0300, Adhemerval Zanella Netto wrote:
> Most recent meeting status is always here:
> https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
> 
> Meeting: 2024-04-01 @ 0900h EST5EDT
> 
> Video/Audio: https://bbb.linuxfoundation.org/room/adm-alk-1uu-7fu
> 
> IRC: #glibc on OFTC.
> 
> Review new patches and attendee requested reviews.
> 
> State NEW delegate NOBODY at 397 patches.
> 
> * 87879: stdlib: reorganize stdlib Makefile routines by functionality
>   - Need more discussion and more information about the issue.
>   - H.J noted he has a patch for bintuils: https://patchwork.sourceware.org/project/binutils/list/?series=29973
> * 87875: elf: sanitize objname in _dl_signal_error
>   - Possible need a bug report.
> * 87870: manual: arith.texi and math.texi fixes
>   - D.J already gave his RB to first two patches, assigning the rest to him.
> * 87853: LoongArch: Add soft floating-point fe* function implementations.
>   - It seems to be rather adding a new ABI, instead of just new symbols.
>   - Florian will add some comments
> * 87852: [v4] LoongArch: Add support for TLS Descriptors
>   - Adhemervall will continue to comment on this one.
> * 87847: Superseeded
> * 87810: OpenRISC glibc hard float support
>   - Skip for now, since this is a quite large patch.

Hello,

Is there anything I should do to help get this reviewed?  Or is self review and
testing good enough for this? I think the patch is not that big, the biggest bit
is the ulps file which I could move out to another patch if that helps.

Perhaps the main thing in this series that I should get right is anthing
related to ABI.  For OpenRISC there are no different calling conventions when
the FPU is enabled so I plan to update the abi list with:

 - soft-float, BE: /lib/ld-linux-or1k.so.1
 - hard-float, BE: /lib/ld-linux-or1k.so.1

ABI list: https://sourceware.org/glibc/wiki/ABIList#nios2

-Stafford

      reply	other threads:[~2024-04-15 15:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 14:00 Adhemerval Zanella Netto
2024-04-15 15:19 ` Stafford Horne [this message]

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=Zh1FgzAu8ZMKH-7v@antec \
    --to=shorne@gmail.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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).