From: Chris Metcalf <cmetcalf@mellanox.com>
To: Joseph Myers <joseph@codesourcery.com>, <libc-alpha@sourceware.org>
Subject: Re: tilepro glibc problems
Date: Fri, 04 Nov 2016 22:25:00 -0000 [thread overview]
Message-ID: <022e73df-567a-980b-7652-a3b43a0d5b2e@mellanox.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611042159080.19848@digraph.polyomino.org.uk>
On 11/4/2016 4:05 PM, Joseph Myers wrote:
> Compile testing of glibc for tilepro (GCC 5, binutils master) shows up two
> problems:
>
> * C++ linking doesn't work (which causes C++ tests in glibc to be
> disabled):
>
> /scratch/jmyers/glibc/many5/install/compilers/tilepro-linux-gnu/lib/gcc/tilepro-glibc-linux-gnu/5.4.1/../../../../tilepro-glibc-linux-gnu/bin/ld:
> a.out: hidden symbol `__atomic_fetch_add_4' in
> /scratch/jmyers/glibc/many5/install/compilers/tilepro-linux-gnu/lib/gcc/tilepro-glibc-linux-gnu/5.4.1/libgcc.a(atomic.o)
> is referenced by DSO
> /scratch/jmyers/glibc/many5/install/compilers/tilepro-linux-gnu/lib/gcc/tilepro-glibc-linux-gnu/5.4.1/../../../../tilepro-glibc-linux-gnu/bin/ld:
> final link failed: Bad value
> collect2: error: ld returned 1 exit status
>
> (This seems to me like your GCC port should be using t-slibgcc-libgcc in
> libgcc/config.host, but I haven't tested that.)
Thanks. I'll forward that on to our compiler guys.
> * sys/dataplane.h includes a header asm/dataplane.h and thereby fails the
> check-installed-headers test because no such header exists in the Linux
> kernel. How is this meant to work? I imagine this would fail for tilegx
> as well if that build didn't fail at an earlier stage.
This header was submitted basically as part of the original glibc patch
series, overlooking the fact that kernel support was not yet upstreamed.
It was intended to support the task isolation patch series in the kernel [1],
but the sys/dataplane.h header targets what you might call the "v0" of that
patch series, namely the version that Tilera shipped customers prior to
starting to upstream it. (At that time it was called "dataplane" support.)
The current API proposal is handled entirely out of linux/prctl.h, so this
header will no longer be necessary; I'll just go ahead and remove it.
--
Chris Metcalf, Mellanox Technologies
http://www.mellanox.com
next prev parent reply other threads:[~2016-11-04 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 22:05 Joseph Myers
2016-11-04 22:25 ` Chris Metcalf [this message]
2016-11-14 16:56 ` [PATCH] Make tile's set_dataplane API compatibility-only Chris Metcalf
2016-11-14 17:00 ` Joseph Myers
2016-11-14 20:05 ` [PATCH v2] " Chris Metcalf
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=022e73df-567a-980b-7652-a3b43a0d5b2e@mellanox.com \
--to=cmetcalf@mellanox.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).