public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>,
	jimw@sifive.com, Alistair Francis <alistair23@gmail.com>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>
Subject: ABI changes still pending for glibc 2.32?
Date: Fri, 26 Jun 2020 12:11:23 -0400	[thread overview]
Message-ID: <c68be61d-fba3-2dd4-9d45-83bf6f55a5fc@redhat.com> (raw)

Community,

What ABI changes are still pending for glibc 2.32?

Jim, You called out RISC-V patches that need review. Do they impact ABI?

Alistair, You called out the semctl_syscall() changes. I assume they impact ABI?

Adhemerval, What is your status reviewing semctl_syscall()?

Vineet, What is the status of the ARC port?

For context I'm considering a few ABI changes to be allowed next week while we
enter "slushy" ABI freeze and I want to narrow that list down.

-- 
Cheers,
Carlos.


             reply	other threads:[~2020-06-26 16:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 16:11 Carlos O'Donell [this message]
2020-06-26 16:28 ` H.J. Lu
2020-06-26 18:25 ` Vineet Gupta
2020-06-26 21:11 ` Alistair Francis
2020-06-29 13:16   ` Adhemerval Zanella
2020-06-26 22:13 ` Szabolcs Nagy
2020-06-27 10:25   ` Florian Weimer
2020-06-27 10:27 ` Florian Weimer
2020-06-30 22:38 ` Andreas K. Huettel
2020-07-03 21:24   ` Carlos O'Donell
2020-07-03 21:52     ` Andreas K. Hüttel
2020-07-08 19:56       ` Carlos O'Donell
2020-07-10 12:59         ` Andreas K. Hüttel
2020-07-10 20:39           ` Carlos O'Donell
2020-07-11 15:16             ` Andreas K. Hüttel
2020-07-11 16:18               ` Florian Weimer
2020-07-11 16:27                 ` Andreas K. Hüttel
2020-07-13 18:38                   ` Carlos O'Donell

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=c68be61d-fba3-2dd4-9d45-83bf6f55a5fc@redhat.com \
    --to=carlos@redhat.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=alistair23@gmail.com \
    --cc=jimw@sifive.com \
    --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).