From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: io-uring Mailing List <[email protected]>
Subject: [GIT PULL liburing] GitHub bot updates 2022-07-11
Date: Mon, 11 Jul 2022 20:50:50 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hello Jens,
GitHub bot updates for liburing:
- Upgrade GitHub bot to Ubuntu 22.04 and gcc-11 (default gcc version on
Ubuntu 22.04).
- Use -O3 optimization.
Please pull!
The following changes since commit 696f28fa0c7eec22bdfade663d31b0f5c6385c77:
Correct mistakes on send/recv* flags (2022-07-09 10:01:32 -0600)
are available in the Git repository at:
https://github.com/ammarfaizi2/liburing.git tags/github-bot-2022-07-11
for you to fetch changes up to bc5868374f371ad3c6b2257ca48ef9e260613c0a:
.github: Use `-O3` flag for GitHub bot (2022-07-11 20:10:58 +0700)
----------------------------------------------------------------
GitHub bot updates for liburing:
- Upgrade GitHub bot to Ubuntu 22.04 and gcc-11.
- Use -O3 optimization.
----------------------------------------------------------------
Ammar Faizi (2):
.github: Upgrade GitHub bot to Ubuntu 22.04 and gcc-11
.github: Use `-O3` flag for GitHub bot
.github/workflows/build.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index fc119cb..333929c 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -7,7 +7,7 @@ on:
jobs:
build:
- runs-on: ubuntu-latest
+ runs-on: ubuntu-22.04
strategy:
fail-fast: false
@@ -84,7 +84,7 @@ jobs:
cxx: mips-linux-gnu-g++
env:
- FLAGS: -g -O2 -Wall -Wextra -Werror
+ FLAGS: -g -O3 -Wall -Wextra -Werror
steps:
- name: Checkout source
--
Ammar Faizi
next reply other threads:[~2022-07-11 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 13:50 Ammar Faizi [this message]
2022-07-11 13:55 ` [GIT PULL liburing] GitHub bot updates 2022-07-11 Jens Axboe
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 \
[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