public inbox for [email protected]
 help / color / mirror / Atom feed
From: Willy Tarreau <[email protected]>
To: "Paul E . McKenney" <[email protected]>
Cc: [email protected], [email protected],
	Ammar Faizi <[email protected]>
Subject: [PATCH 0/2] nolibc: fix two build issues at -O0
Date: Wed, 23 Mar 2022 08:18:05 +0100	[thread overview]
Message-ID: <[email protected]> (raw)

Hello Paul,

please find in this series two build fixes to apply on top of the series
you've already queued:
 - gcc errors at -O0 because it doesn't eliminate non-inline code and
   keeps the reference to the external "environ" from getenv()
 - clang fails at -O0 because __builtin_strlen() calls strlen()

I don't care about optimizing at -O0 by definition but at least it should
build and work correctly! I've verified that rcutorture still runs.

Thanks!
Willy

---
Willy Tarreau (2):
  tools/nolibc/string: do not use __builtin_strlen() at -O0
  tools/nolibc/stdlib: only reference the external environ when inlined

 tools/include/nolibc/stdlib.h | 22 +++++++++++++++-------
 tools/include/nolibc/string.h | 11 ++++++++++-
 2 files changed, 25 insertions(+), 8 deletions(-)

-- 
2.35.1



             reply	other threads:[~2022-03-23  7:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23  7:18 Willy Tarreau [this message]
2022-03-23  7:18 ` [PATCH 1/2] tools/nolibc/string: do not use __builtin_strlen() at -O0 Willy Tarreau
2022-03-23  7:18 ` [PATCH 2/2] tools/nolibc/stdlib: only reference the external environ when inlined Willy Tarreau
2022-03-23 13:36   ` Ammar Faizi
2022-03-23 23:16 ` [PATCH 0/2] nolibc: fix two build issues at -O0 Paul E. McKenney

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] \
    [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