From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Cc: Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH 0/2] Fix incorrect stub warnings after generic refactor
Date: Mon, 19 Dec 2022 09:16:58 -0300 [thread overview]
Message-ID: <dc265a5e-492c-828c-1988-41185f9f6b55@linaro.org> (raw)
In-Reply-To: <cover.1671451274.git.fweimer@redhat.com>
On 19/12/22 09:03, Florian Weimer wrote:
> They cause link failures with -Wl,--fatal-warnings on aarch64.
>
Would be possible to use this option as default to catch such errors?
> Tested on aarch64-linux-gnu, i686-linux-gnu, x86_64-linux-gnu. Manually
> verified that the warnings are gone on aarch64-linux-gnu.
>
> Florian Weimer (2):
> Linux: Reflow and sort some Makefile variables
> Linux: Remove epoll_create, inotify_init from syscalls.list
>
> sysdeps/unix/sysv/linux/Makefile | 220 ++++++++++++++++++--------
> sysdeps/unix/sysv/linux/syscalls.list | 2 -
> 2 files changed, 157 insertions(+), 65 deletions(-)
>
>
> base-commit: 0fb10e49ad169374650534509767ec1d4232e230
next prev parent reply other threads:[~2022-12-19 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 12:03 Florian Weimer
2022-12-19 12:03 ` [PATCH 1/2] Linux: Reflow and sort some Makefile variables Florian Weimer
2022-12-19 12:15 ` Adhemerval Zanella Netto
2022-12-19 12:03 ` [PATCH 2/2] Linux: Remove epoll_create, inotify_init from syscalls.list Florian Weimer
2022-12-19 12:16 ` Adhemerval Zanella Netto
2022-12-19 12:16 ` Adhemerval Zanella Netto [this message]
2022-12-19 12:27 ` [PATCH 0/2] Fix incorrect stub warnings after generic refactor Florian Weimer
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=dc265a5e-492c-828c-1988-41185f9f6b55@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.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).