From: Peter Zijlstra <peterz@infradead.org>
To: Chris Metcalf <cmetcalf@mellanox.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: linux-next: Tree for Jun 21
Date: Tue, 21 Jun 2016 16:25:25 +0200 [thread overview]
Message-ID: <20160621142525.GF3704@worktop> (raw)
In-Reply-To: <2c751e92-9dcb-a42c-7ecb-764d3974c1e4@mellanox.com>
On Tue, Jun 21, 2016 at 10:20:39AM -0400, Chris Metcalf wrote:
> On 6/21/2016 10:14 AM, Peter Zijlstra wrote:
> >On Tue, Jun 21, 2016 at 04:04:08PM +0200, Peter Zijlstra wrote:
> >>>I'm not sure who builds the toolchains, but tilepro is in upstream gcc/binutils/etc
> >>>so should be easy enough to include. There's also a cross-toolchain for x64 I put
> >>>up a while ago [1] that you could grab if you wanted to try it.
> >>I usually build my own set -- and just did. But tilepro was not
> >>included. Lemme go do so.
> >binutils-2_26-branch builds for tilepro-linux
> >gcc-6-branch does _not_ build for tilepro-linux
>
> That's unexpected. I'll pass this over to our compiler folks. Thanks!
If you need more info like gcc-configure, gcc-build logs or exact
gcc-6-branch commitid, please let me know.
next prev parent reply other threads:[~2016-06-21 14:25 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 5:46 linux-next: Tree for Jun 21 Stephen Rothwell
2016-06-21 7:01 ` Sudip Mukherjee
2016-06-21 7:58 ` Peter Zijlstra
2016-06-21 8:55 ` Sudip Mukherjee
2016-06-21 12:08 ` Chris Metcalf
2016-06-21 12:08 ` Chris Metcalf
2016-06-21 12:42 ` Peter Zijlstra
2016-06-21 13:47 ` Chris Metcalf
2016-06-21 13:47 ` Chris Metcalf
2016-06-21 14:04 ` Peter Zijlstra
2016-06-21 14:14 ` Peter Zijlstra
2016-06-21 14:14 ` Peter Zijlstra
2016-06-21 14:20 ` Chris Metcalf
2016-06-21 14:20 ` Chris Metcalf
2016-06-21 14:25 ` Peter Zijlstra [this message]
2016-06-21 14:34 ` Sudip Mukherjee
2016-06-21 15:26 ` Chris Metcalf
2016-06-21 15:26 ` Chris Metcalf
2016-06-21 17:06 ` Peter Zijlstra
2016-06-21 17:29 ` Peter Zijlstra
2016-06-21 18:28 ` Peter Zijlstra
2016-06-21 18:36 ` Chris Metcalf
2016-06-21 18:36 ` Chris Metcalf
2016-06-21 18:50 ` Peter Zijlstra
2016-06-21 19:04 ` Peter Zijlstra
2016-06-21 21:14 ` Arnd Bergmann
2016-06-22 20:43 ` Chris Metcalf
2016-06-22 20:43 ` Chris Metcalf
2016-06-22 21:05 ` Peter Zijlstra
2016-06-22 9:16 ` Peter Zijlstra
2016-06-22 20:40 ` Chris Metcalf
2016-06-22 20:40 ` Chris Metcalf
2016-06-24 8:58 ` [tip:locking/arch-atomic] locking/atomic, arch/tile: Fix tilepro build tip-bot for Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2024-06-21 18:36 linux-next: Tree for Jun 21 Mark Brown
2023-06-21 4:59 Stephen Rothwell
2022-06-21 9:35 Stephen Rothwell
2021-06-21 12:16 Stephen Rothwell
2020-06-21 15:23 Stephen Rothwell
2019-06-21 11:01 Stephen Rothwell
2018-06-21 4:11 Stephen Rothwell
2017-06-21 8:09 Stephen Rothwell
2015-06-21 10:50 Stephen Rothwell
2013-06-21 8:17 Stephen Rothwell
2013-06-21 8:17 ` Stephen Rothwell
2012-06-21 6:12 Stephen Rothwell
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=20160621142525.GF3704@worktop \
--to=peterz@infradead.org \
--cc=cmetcalf@mellanox.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sudipm.mukherjee@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.