public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@mellanox.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Library directories for tilegx
Date: Mon, 07 Nov 2016 21:48:00 -0000	[thread overview]
Message-ID: <b597dff8-ca2b-9859-0186-b619cd34f75b@mellanox.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611071623120.3948@digraph.polyomino.org.uk>

On 11/7/2016 11:25 AM, Joseph Myers wrote:
> On Thu, 3 Nov 2016, Chris Metcalf wrote:
>
>> On 11/3/2016 7:08 PM, Joseph Myers wrote:
>>> Incidentally, I found another issue in building: GCC has a tilegxbe-*
>>> target name for big-endian, but sysdeps/tile/preconfigure only handles
>>> tilegx, not tilegxbe.  However, that's easy to work around by configuring
>>> glibc for a different triplet from GCC.
>> Good point.  I don't actually test tilegxbe; I don't think we ever had a lot
>> of interest in that version of the toolchain.  I will try to remember to add
>> it next time I do tests, and I can push up a fix to preconfigure at that point
>> too (or feel free to push one yourself).
> In fact there are more problems:
>
> * Using GCC 6 branch, the tilegxbe build fails with an ICE building libgcc
> in the first GCC build.
>
> * Using GCC mainline, I get ICEs building libgcc for both tilegx and
> tilegxbe.

Thanks - I've passed these on to our compiler team as well.

-- 
Chris Metcalf, Mellanox Technologies
http://www.mellanox.com

  reply	other threads:[~2016-11-07 21:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04  0:44 Joseph Myers
2016-11-04  1:01 ` Chris Metcalf
2016-11-04  1:08   ` Joseph Myers
2016-11-04  1:50     ` Chris Metcalf
2016-11-04 13:33       ` Joseph Myers
2016-11-04 15:12         ` Chris Metcalf
2016-11-07 16:26       ` Joseph Myers
2016-11-07 21:48         ` Chris Metcalf [this message]
2016-11-09  0:35   ` Joseph Myers
2016-11-14 20:12     ` Chris Metcalf
2016-11-14 22:59       ` Joseph Myers
2016-11-14 23:25         ` 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=b597dff8-ca2b-9859-0186-b619cd34f75b@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).