From: Tony Breeds <tony@bakeyournoodle.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Jason Baron <jbaron@redhat.com>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, mingo@elte.hu, hpa@zytor.com,
tglx@linutronix.de, rostedt@goodmis.org, andi@firstfloor.org,
roland@redhat.com, rth@redhat.com, mhiramat@redhat.com,
fweisbec@gmail.com, avi@redhat.com, vgoyal@redhat.com,
sam@ravnborg.org
Subject: Re: [PATCH 00/13] jump label v9
Date: Fri, 18 Jun 2010 13:45:39 +1000 [thread overview]
Message-ID: <20100618034539.GD16706@ozlabs.org> (raw)
In-Reply-To: <20100615154440.GA9224@Krystal>
On Tue, Jun 15, 2010 at 11:44:40AM -0400, Mathieu Desnoyers wrote:
> It makes me wonder if anyone had success building a gcc 4.5
> Intel-to-sparc64 cross-compiler ? Usually, the crosstool-like suites are
> a few versions behind. I'm aware that this is not trivial, as
> cross-compilers have a tendency to refuse to get built in certain
> occasions (such as being a recent less tested version). I'd recommend
> you focus on this as a first step before resubmitting.
I'm building (and uploading to kernel.org[1]) 4.4.4 and 4.5.0 toolchains.
They're untested on anything otyher than the system I built them on.
Give it 24 hours and then try'em
Yours Tony
[1] http://kernel.org/pub/tools/crosstool/files/bin/${host_arch}/ [2]
[2] currently only i686 and x86_64, powerpc64 are comming.
next prev parent reply other threads:[~2010-06-18 3:45 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 21:38 [PATCH 00/13] jump label v9 Jason Baron
2010-06-09 21:38 ` [PATCH 01/13] jump label v9: notifier atomic call chain notrace Jason Baron
2010-06-09 21:58 ` Frederic Weisbecker
2010-06-10 15:34 ` Jason Baron
2010-06-09 21:38 ` [PATCH 02/13] jump label v9: base patch Jason Baron
2010-06-09 22:35 ` Frederic Weisbecker
2010-06-10 15:44 ` Jason Baron
2010-06-10 16:22 ` Ingo Molnar
2010-06-10 17:11 ` Frederic Weisbecker
2010-06-09 22:36 ` Frederic Weisbecker
2010-06-10 12:06 ` Peter Zijlstra
2010-06-10 12:18 ` Peter Zijlstra
2010-06-09 21:39 ` [PATCH 03/13] jump label v9: x86 support Jason Baron
2010-06-10 12:12 ` Peter Zijlstra
2010-06-10 12:14 ` Ingo Molnar
2010-06-10 13:26 ` Andi Kleen
2010-06-10 14:12 ` Peter Zijlstra
2010-06-10 14:28 ` Andi Kleen
2010-06-10 15:37 ` Ingo Molnar
2010-06-10 16:24 ` Andi Kleen
2010-06-11 8:12 ` Ingo Molnar
2010-06-11 8:30 ` Andi Kleen
2010-06-10 16:29 ` Steven Rostedt
2010-06-10 15:04 ` Jason Baron
2010-06-10 16:13 ` Mathieu Desnoyers
2010-06-11 0:52 ` Jason Baron
2010-06-11 6:18 ` H. Peter Anvin
2010-06-11 7:58 ` Ingo Molnar
2010-06-10 12:15 ` Peter Zijlstra
2010-06-10 12:33 ` Peter Zijlstra
2010-06-09 21:39 ` [PATCH 04/13] jump label v9: tracepoint support Jason Baron
2010-06-10 12:22 ` Peter Zijlstra
2010-06-09 21:39 ` [PATCH 05/13] jump label v9: add module support Jason Baron
2010-06-09 21:39 ` [PATCH 06/13] jump label v9: move ftrace_dyn_arch_init to common code Jason Baron
2010-06-19 3:24 ` Steven Rostedt
2010-06-09 21:39 ` [PATCH 07/13] jump label v9: sort jump table at build-time Jason Baron
2010-06-09 21:39 ` [PATCH 08/13] jump label v9: initialize workqueue tracepoints *before* they are registered Jason Baron
2010-06-09 21:39 ` [PATCH 09/13] jump label v9: jump_label_text_reserved() to reserve our jump points Jason Baron
2010-06-09 21:39 ` [PATCH 10/13] jump label v9: convert jump label to use a key Jason Baron
2010-06-10 12:38 ` Peter Zijlstra
2010-06-10 12:43 ` Peter Zijlstra
2010-06-10 13:57 ` Jason Baron
2010-06-10 14:46 ` Peter Zijlstra
2010-06-09 21:39 ` [PATCH 11/13] jump label v9: convert dynamic debug to use jump labels Jason Baron
2010-06-09 21:39 ` [PATCH 12/13] jump label v9: sparc64 add jump_label support Jason Baron
2010-06-09 21:39 ` [PATCH 13/13] jump label v9: add docs Jason Baron
2010-06-10 12:49 ` Peter Zijlstra
2010-06-15 3:47 ` [PATCH 00/13] jump label v9 David Miller
2010-06-15 14:28 ` Jason Baron
2010-06-15 15:44 ` Mathieu Desnoyers
2010-06-18 3:45 ` Tony Breeds [this message]
2010-06-18 15:18 ` Mathieu Desnoyers
2010-06-15 17:13 ` David Miller
2010-06-15 17:28 ` H. Peter Anvin
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=20100618034539.GD16706@ozlabs.org \
--to=tony@bakeyournoodle.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=rth@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.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.