From: Gerlando Falauto <gerlando.falauto@keymile.com>
To: loody <miloody@gmail.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>,
gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: compile lttng get gcc compile error
Date: Wed, 14 May 2014 16:52:49 +0200 [thread overview]
Message-ID: <53738341.4030706@keymile.com> (raw)
In-Reply-To: <CANudz+tzfc0cjBh=7Jm4TPvm7h33oyPaZdVGBjeuOrzgM8gimQ@mail.gmail.com>
Hi loody,
[originally posted to gcc-help, cross-posting to lttng-dev]
On 03/27/2014 01:37 PM, loody wrote:
> hi Jonathan:
>
> 2014-03-27 18:43 GMT+08:00 Jonathan Wakely <jwakely.gcc@gmail.com>:
>> On 27 March 2014 10:32, loody wrote:
>>> hi all
>>> when I try to cross-compile lttng-tool for arm.
>>> I get below message
>>>
>>> CC kernel-consumer.lo
>>> kernel-consumer.c: In function 'lttng_kconsumer_snapshot_channel':
>>> kernel-consumer.c:324:1: internal compiler error: in gen_movsi, at
>>> config/arm/arm.md:5680
>>>
>>> my gcc version is 4.7.4
>>
>> I think this is http://gcc.gnu.org/PR58595 which will be fixed in GCC 4.9.0
> is there any patch I can use to fix this issue before waiting 4.9.0 release?
> or is there method I can avoid this compile happen if I rewrite the source?
>
> thanks a lot,
>
Did you ever find a workaround for such an issue? Perhaps by refactoring
the code within lttng_kconsumer_snapshot_channel()?
Thank you!
Gerlando
next parent reply other threads:[~2014-05-14 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANudz+u_d54BtB9Fk3Vdtb8B7im_WMbK20jg_zUGeJ3wEPECMg@mail.gmail.com>
[not found] ` <CAH6eHdSvfWjiZCLUNHaftnwjp_L56uSPwA=hTHpLAwiPhunfsA@mail.gmail.com>
[not found] ` <CANudz+tzfc0cjBh=7Jm4TPvm7h33oyPaZdVGBjeuOrzgM8gimQ@mail.gmail.com>
2014-05-14 14:52 ` Gerlando Falauto [this message]
2014-05-14 19:56 ` [lttng-dev] compile lttng get gcc compile error Mathieu Desnoyers
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=53738341.4030706@keymile.com \
--to=gerlando.falauto@keymile.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lttng-dev@lists.lttng.org \
--cc=miloody@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.