From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/6] lttng-modules: Exclude arm
Date: Thu, 06 Mar 2014 12:45:44 -0600 [thread overview]
Message-ID: <1394131544.28420.58.camel@empanada> (raw)
In-Reply-To: <1394129048.24424.271.camel@phil-desktop.brightsign>
On Thu, 2014-03-06 at 18:04 +0000, Phil Blundell wrote:
> On Thu, 2014-03-06 at 11:09 -0600, Tom Zanussi wrote:
> > +# lttng currently blacklists arm with gcc-4.8
> > +COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
>
> If the issue at hand here is GCC PR 58854 (which the lttng mailing list
> thread seems to suggest it is), can't we just apply the patch for it
> rather than disabling lttng-modules altogether?
>
Well, I think it's more than that - there's apparently an unbalanced
preempt_disable in lttng somewhere that's the real root of the problem:
http://gcc.gnu.org/ml/gcc/2013-11/msg00393.html
So lttng is still broken, and the blacklist is still in place in the
lttng code.
Tom
> p.
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2014-03-06 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 17:09 [PATCH 0/6] lttng update (add 2.4.0) Tom Zanussi
2014-03-06 17:09 ` [PATCH 1/6] lttng-modules: Add version 2.4.0 Tom Zanussi
2014-03-06 17:09 ` [PATCH 2/6] lttng-tools: " Tom Zanussi
2014-03-06 17:09 ` [PATCH 3/6] lttng-ust: " Tom Zanussi
2014-03-06 17:09 ` [PATCH 4/6] lttng-modules: Exclude arm Tom Zanussi
2014-03-06 17:56 ` Phil Blundell
2014-03-06 18:36 ` Tom Zanussi
2014-03-06 18:04 ` Phil Blundell
2014-03-06 18:45 ` Tom Zanussi [this message]
2014-03-06 17:09 ` [PATCH 5/6] lttng-modules: Fix 3.14 bio tracepoints Tom Zanussi
2014-03-06 17:09 ` [PATCH 6/6] lttng-ust: Disable doc/examples in the build Tom Zanussi
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=1394131544.28420.58.camel@empanada \
--to=tom.zanussi@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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