From: Jeff Law <jeffreyalaw@gmail.com>
To: Stafford Horne <shorne@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>, newlib@sourceware.org
Subject: Re: nds broken by recent patches
Date: Fri, 28 Jan 2022 20:28:09 -0700 [thread overview]
Message-ID: <a3336eee-5e04-da19-d259-38fc4e1e2732@gmail.com> (raw)
In-Reply-To: <YfSidWq9GD+npNsT@antec>
On 1/28/2022 7:12 PM, Stafford Horne wrote:
> On Fri, Jan 28, 2022 at 05:58:46PM -0700, Jeff Law wrote:
>>
>> On 1/28/2022 4:32 PM, Stafford Horne wrote:
>>> On Fri, Jan 28, 2022 at 02:54:24PM -0700, Jeff Law wrote:
>>>> Replying to myself...
>>>>
>>>> On 1/28/2022 9:36 AM, Jeff Law wrote:
>>>>> For example, someone mucked up the compiler for or1k-elf at the same
>>>>> time you're doing your refactoring. Now I've got a patch to fix the
>>>>> compiler ICE, *but* I'm also getting a crap-ton of new testsuite
>>>>> failures in the testsuite due to missing _init/_fini symbols. I don't
>>>>> know yet if that's a newlib issue or something else mucked up on the
>>>>> compiler side.
>>>> I think I've tracked this done. The change to internalize
>>>> HAVE_INITFINI_ARRAY wasn't complete. It missed newlib. Affects aarch64,
>>>> arm, or1k and cris -elf ports. I don't test for former pair, but I do test
>>>> the latter pair. or1k and cris fail differently. or1k-elf code fails to
>>>> link, while cris-elf fails a few tests that rely on ctor/dtor support.
>>> Is there anything I can help with here for or1k-elf? Or was this something I
>>> did wrong with ff7b7b894 ("libgloss: or1k: If available call the init for
>>> init_array")?
>> It's a trivial goof in some recent refactoring in newlib.
>>
>>> I haven't rebuilt my newlib toolchain since last year or so.
>> Which raises an interesting set of questions. Is or1k at a point where we
>> can cross build glibc & the kernel using upstream bits? Is qemu user mode
>> emulation available? The former pair would be a step forward from a testing
>> standpoint. If we had the latter too, then we could build a rootfs and do
>> native 3-stage testing in a chroot.
> Now that glibc is upstream I guess the answer is yes.
>
> I have been building a buildroot using my glibc braches/now on master (maybe
> some buildroot patches need to be upstreamed to tell buildroot or1k has glibc
> support).
I don't use the builtroot project to construct mine. Though perhaps I
should ;-)
>
> With that we can test using qemu user mode. I used to use qemu user mode to test
> the glibc test-suite but not all syscalls are emulated so there were some tests
> that would fail.
Yea, I'm much more concerned about testing GCC and 3-staging using qemu
user mode & running the testsuite does a much more thorough job than
just building newlib and running the gcc testsuite.
Thanks. Clearly I've got a little project on the horizon.
jeff
next prev parent reply other threads:[~2022-01-29 3:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171dc9cb-6b2c-ead3-1c55-27fadb33220f@gmail.com>
2022-01-28 10:23 ` [PATCH 1/2] newlib: fix preprocessor checks Mike Frysinger
2022-01-28 10:23 ` [PATCH 2/2] newlib: add AC_CACHE_CHECK sugar around " Mike Frysinger
2022-01-31 14:20 ` Corinna Vinschen
2022-01-31 14:18 ` [PATCH 1/2] newlib: fix " Corinna Vinschen
[not found] ` <YfPDA/LVL745V+02@vapier>
2022-01-28 16:36 ` nds broken by recent patches Jeff Law
2022-01-28 21:54 ` Jeff Law
2022-01-28 23:32 ` Stafford Horne
2022-01-29 0:58 ` Jeff Law
2022-01-29 2:12 ` Stafford Horne
2022-01-29 3:28 ` Jeff Law [this message]
2022-01-29 5:15 ` Mike Frysinger
2022-01-29 5:12 ` [PATCH/committed] libgloss: update Makefile regen rules for merged arches Mike Frysinger
2022-01-29 5:13 ` nds broken by recent patches Mike Frysinger
2022-01-31 14:34 ` R. Diez
2022-02-01 17:25 ` Jeff Law
2022-02-02 10:23 ` Mike Frysinger
2022-02-02 20:59 ` Jeff Law
2022-02-03 16:11 ` libgloss multilib installs broken [was nds broken by recent patches] Jeff Law
2022-02-04 5:45 ` Mike Frysinger
2022-02-07 15:40 ` Jeff Law
2022-02-04 8:55 ` [PATCH] libgloss: restore multilib settings in subdir makefiles Mike Frysinger
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=a3336eee-5e04-da19-d259-38fc4e1e2732@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=newlib@sourceware.org \
--cc=shorne@gmail.com \
--cc=vapier@gentoo.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).