From: Joseph Myers <joseph@codesourcery.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "libc-alpha @ sourceware . org" <libc-alpha@sourceware.org>,
<linux-snps-arc@lists.infradead.org>,
<Cupertino.Miranda@synopsys.com>
Subject: Re: [RFC 4/6] ARC: Initial port to glibc
Date: Thu, 29 Jun 2017 15:29:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1706291526330.7727@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5a738e1a-fac6-3dbb-3c3f-744b12966dd7@synopsys.com>
On Thu, 29 Jun 2017, Vineet Gupta wrote:
> I regenerated the ABI files, but it seems generated libc abilist is lacking
> malloc_{get,set}_stated and had to be added manually - which causes a
> subsequent testsuite failure. Is this (manual addition of entries to abi file)
> correct or is this a deficiency of ARC port.
malloc_get_state and malloc_set_state have been obsoleted, meaning that
they are not included in any new ports, are not included in static libc
for any port and in shared libc in existing ports they are compat symbols
that new binaries can't be linked against. (Yes, the testsuite work to
support ports postdating that obsoletion is still needed.)
> Speaking of testsuite, since this is bootstrapping a glibc system we have to
> resort to using scripts/cross-test-ssh.sh which is a serious pain in the neck.
> Is there no easy way to build the whole test suite first and then just run it
> on target.
You can probably build the testsuite with "make check" without setting
test-wrapper, presuming you've fixed all issues with compilation of the
testsuite, then rerun "make check" with test-wrapper specified to run the
execution tests. I don't know whether transferring the build directory to
a different system for a native "make check" would work, but at least lots
of tools would be required on the target to do so.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-06-29 15:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 8:01 [RFC 0/6] glibc port to ARC architecture Vineet Gupta
2017-06-27 8:01 ` [RFC 1/6] upstream: comment update Vineet Gupta
2017-06-27 8:01 ` [RFC 5/6] ARC: Enable __start as entry point vs. canonical _start Vineet Gupta
2017-06-27 8:01 ` [RFC 2/6] ARC: Fixed inline asm contraints to gcc 6.x Vineet Gupta
2017-06-27 11:47 ` Joseph Myers
2017-06-27 16:40 ` Vineet Gupta
2017-06-27 16:54 ` Zack Weinberg
2017-06-27 8:01 ` [RFC 6/6] ARC: Fix several testsuite failures related to unwinding Vineet Gupta
2017-06-27 8:01 ` [RFC 3/6] ARC: add definitions to elf/elf.h Vineet Gupta
2017-06-27 8:02 ` [RFC 4/6] ARC: Initial port to glibc Vineet Gupta
2017-06-27 11:30 ` Florian Weimer
2017-06-27 11:55 ` Vineet Gupta
2017-06-27 12:01 ` Florian Weimer
2017-06-27 12:03 ` Joseph Myers
2017-06-27 11:56 ` Joseph Myers
2017-06-27 15:51 ` Vineet Gupta
2017-06-27 15:55 ` Joseph Myers
2017-06-27 16:52 ` Vineet Gupta
2017-06-27 17:02 ` Joseph Myers
2017-06-27 19:32 ` Vineet Gupta
2017-06-27 19:56 ` Joseph Myers
2017-06-28 8:49 ` ucontect vs. ucontext_t (was Re: [RFC 4/6] ARC: Initial port to glibc) Vineet Gupta
2017-06-28 9:23 ` Szabolcs Nagy
2017-06-28 9:30 ` Joseph Myers
2017-06-28 9:42 ` Vineet Gupta
2017-06-29 15:22 ` [RFC 4/6] ARC: Initial port to glibc Vineet Gupta
2017-06-29 15:29 ` Joseph Myers [this message]
2017-11-06 20:19 ` Vineet Gupta
2017-11-06 22:27 ` Joseph Myers
2017-06-27 11:31 ` [RFC 0/6] glibc port to ARC architecture Florian Weimer
2017-06-27 12:00 ` Joseph Myers
2017-11-06 22:52 ` Vineet Gupta
2017-11-06 23:09 ` Joseph Myers
2017-11-27 20:37 ` Vineet Gupta
2017-11-27 22:16 ` Joseph Myers
2017-12-08 0:31 ` Vineet Gupta
2017-12-08 11:15 ` Joseph Myers
2017-06-27 11:45 ` Joseph Myers
2017-06-27 13:16 ` Vineet Gupta
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=alpine.DEB.2.20.1706291526330.7727@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Cupertino.Miranda@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.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).