From: Joel Sherrill <joel@rtems.org>
To: Keith Packard <keithp@keithp.com>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: Making newlib tests work again
Date: Mon, 16 Dec 2019 22:09:00 -0000 [thread overview]
Message-ID: <CAF9ehCWMK5gCU4FYkTG-e1or9BtmtqdVvoKnbieTUydN+hTS1A@mail.gmail.com> (raw)
In-Reply-To: <87sglk0wh2.fsf@keithp.com>
Personally, I'd like to see the tests working. I would like to see them
running on RTEMS.
--joel
On Mon, Dec 16, 2019 at 3:52 PM Keith Packard <keithp@keithp.com> wrote:
>
> I spent a bunch of time over the last couple of weeks getting the newlib
> tests running again in my 'picolibc' fork. In the process, I found a few
> bugs in the library which I've got patches for, but I'm wondering if
> anyone here has any interest in having the test fixes merged in. I'm not
> sure how useful they would be in the newlib tree as I'm not sure how to
> run them here.
>
> The 'big' change was to re-generate all of the math test cases using
> glibc on x86-64. There's code in the libm tests to re-emit the C code
> which I used for that. For the string conversion tests, I cobbled some
> hacks together.
>
> The newlib code I'm using now passes all of the tests on
> x86-64-linux-gnu, i686-linux-gnu, arm-none-eabi and
> riscv64-unknown-elf. For riscv64-unknown-elf, qemu is able to emulate
> all possible processor configurations and I'm testing them all (30
> different newlib builds). For arm-none-eabi, I'm only testing cortex-m3
> for now (qemu-system-arm is not as flexible as qemu-system-riscv32/
> qemu-system-riscv64).
>
> I don't want to spam the list with a large set of huge patches unless
> there's some interest in them; for now, I've got them sitting on github:
>
> https://github.com/keith-packard/picolibc/tree/fixes-newlib
>
> --
> -keith
>
next prev parent reply other threads:[~2019-12-16 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 21:52 "Keith Packard"
2019-12-16 22:09 ` Joel Sherrill [this message]
2019-12-16 23:31 ` Keith Packard
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=CAF9ehCWMK5gCU4FYkTG-e1or9BtmtqdVvoKnbieTUydN+hTS1A@mail.gmail.com \
--to=joel@rtems.org \
--cc=keithp@keithp.com \
--cc=newlib@sourceware.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 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).