From: Adrian Bunk <bunk@stusta.de>
To: Jonathan Richardson <jonathan.richardson@broadcom.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] fio: upgrade 3.17 -> 3.18
Date: Wed, 19 Feb 2020 00:09:22 +0200 [thread overview]
Message-ID: <20200218220922.GA24326@localhost> (raw)
In-Reply-To: <CAHrpVsXMkZydpmbXPdQJo5qW1=DpJTqSUghNjTnZahqCg7hj9Q@mail.gmail.com>
On Tue, Feb 18, 2020 at 11:37:33AM -0800, Jonathan Richardson via Openembedded-devel wrote:
> I was just about to submit a patch to remove the disabling of compiler
> optimizations to fio. On our cortex A72 this kills the performance of fio
> by 25%. That would solve this build issue also.
>...
> > https://errors.yoctoproject.org/Errors/Details/391129/
>...
t/io_uring.c:103:17: error: '__NR_sys_io_uring_register' undeclared (first use in this function); did you mean 'SYS_io_uring_register'?
This error does not look related to optimization.
This looks like https://github.com/axboe/fio/issues/923
cu
Adrian
next prev parent reply other threads:[~2020-02-18 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 23:43 [meta-oe][PATCH] cryptsetup: upgrade 2.2.2 -> 2.3.0 Wang Mingyu
2020-02-14 23:43 ` [meta-oe][PATCH] fio: upgrade 3.17 -> 3.18 Wang Mingyu
2020-02-15 8:40 ` Khem Raj
2020-02-18 19:37 ` Jonathan Richardson
2020-02-18 22:09 ` Adrian Bunk [this message]
2020-02-19 0:37 ` Jonathan Richardson
2020-02-19 2:36 ` Khem Raj
2020-02-14 23:43 ` [meta-oe][PATCH] hwdata: upgrade 0.331 -> 0.332 Wang Mingyu
2020-02-14 23:43 ` [meta-oe][PATCH] libdbi-perl: upgrade 1.642 -> 1.643 Wang Mingyu
2020-02-14 23:43 ` [meta-oe][PATCH] libp11: upgrade 0.4.10 -> 11 Wang Mingyu
2020-02-27 17:52 ` Ricardo Salveti
2020-02-27 17:57 ` Ricardo Salveti
2020-02-27 19:02 ` Khem Raj
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=20200218220922.GA24326@localhost \
--to=bunk@stusta.de \
--cc=jonathan.richardson@broadcom.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.