public inbox for
help / color / mirror / Atom feed
From: Thomas Schwinge <>
Subject: [newlib-cygwin] nvptx: Remove newlib ELIX level 1 restriction
Date: Fri, 20 Jan 2023 19:36:54 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=654072d7a2feadb7b4d7466e59105198ab5e0968

commit 654072d7a2feadb7b4d7466e59105198ab5e0968
Author: Thomas Schwinge <>
Date:   Wed Sep 21 18:58:34 2022 +0200

    nvptx: Remove newlib ELIX level 1 restriction
    Such a hard-coded ELIX level restriction is only being applied for nvptx
    newlib -- but we'd actually like higher levels' functions available there,
    too.  (Users continue to be able to override this via newlib 'configure',
    as for every other newlib target.)
    This already enables GCC test cases that currently FAIL due to
    'unresolved symbol strndup' ('gcc.dg/builtin-dynamic-object-size-0.c'), or
    'unresolved symbol mempcpy' ('gcc.dg/torture/pr45636.c'), for example.
    Co-authored-by: Andrew Stubbs <>

 newlib/NEWS           | 1 +
 newlib/ | 5 -----
 2 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/newlib/NEWS b/newlib/NEWS
index 9aa82920d..ee456f9b8 100644
--- a/newlib/NEWS
+++ b/newlib/NEWS
@@ -13,6 +13,7 @@
 - use global stdio streams for all configurations
 - use global atexit data for all configurations
 - vectorized math routines added for amdgcn platform
+- nvptx: remove newlib ELIX level 1 restriction
 *** Major changes in newlib version 4.2.0:
diff --git a/newlib/ b/newlib/
index 7157877ff..0a1ba282a 100644
--- a/newlib/
+++ b/newlib/
@@ -938,11 +938,6 @@ fi
 # Target-specific defaults
 case "${host_cpu}" in
-	if [ "x${newlib_elix_level}" = "x0" ]; then
-		newlib_elix_level=1;
-	elif [ "x${newlib_elix_level}" != "x1" ]; then
-		newlib_msg_warn="nvptx does not support elix level > 1";
-	fi
 	if [[ -z ${newlib_global_stdio_streams} ]]; then

                 reply	other threads:[~2023-01-20 19:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).