From: Alviro Iskandar Setiawan <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Stefan Hajnoczi <[email protected]>,
[email protected],
Ammar Faizi <[email protected]>,
Jens Axboe <[email protected]>, Jeff Moyer <[email protected]>,
Guillem Jover <[email protected]>
Subject: Re: False positives in nolibc check
Date: Tue, 20 Jun 2023 23:16:26 +0700 [thread overview]
Message-ID: <CAOG64qO4Dj9OM1R_tT-+=TeCpV5wdnzmFEJ1YqLjYtpNZB1UEw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Tue, Jun 20, 2023 at 10:49 PM Ammar Faizi <[email protected]> wrote:
> Can you mention other dependencies that do need libc? That information
> would be useful to consider bringing back libc to liburing.
The recent memset() problem is another example of it. It seems that
the compiler on aarch64 replaces a zeroing struct operation with a
call to memset(). I usually see the same memset() insertion on x86-64
too. I thought -ffreestanding will make the compiler not generate a
memset() call when zeroing a struct or array. Not sure about it.
-- Viro
next prev parent reply other threads:[~2023-06-20 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 13:31 False positives in nolibc check Stefan Hajnoczi
2023-06-20 14:39 ` Alviro Iskandar Setiawan
2023-06-21 9:47 ` Stefan Hajnoczi
2023-06-20 15:49 ` Ammar Faizi
2023-06-20 16:16 ` Alviro Iskandar Setiawan [this message]
2023-06-21 10:04 ` Stefan Hajnoczi
2023-06-21 10:19 ` Ammar Faizi
2023-06-21 11:51 ` Guillem Jover
2023-06-21 16:08 ` Ammar Faizi
2023-07-12 15:00 ` Stefan Hajnoczi
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='CAOG64qO4Dj9OM1R_tT-+=TeCpV5wdnzmFEJ1YqLjYtpNZB1UEw@mail.gmail.com' \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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