From: stefan_seefeld@mentor.com (Stefan Seefeld)
Subject: [lttng-dev] arm gcc compile lttng-tool fail
Date: Thu, 27 Mar 2014 08:58:38 -0400 [thread overview]
Message-ID: <5334207E.1030007@mentor.com> (raw)
In-Reply-To: <CANudz+voc=OGJXU4NViC38q2K7z1LwMnC5ZeAEAF=L+831AK2w@mail.gmail.com>
On 2014-03-27 08:53, loody wrote:
> hi stefan:
>
> 2014-03-27 20:41 GMT+08:00 Stefan Seefeld <stefan_seefeld at mentor.com>:
>> On 2014-03-27 08:26, loody wrote:
>>> hi all:
>>> I try to compile lttng-tool for arm platform but 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
>>>
>>> after ask gcc for help, they said this will be fixed in gcc 4.9.0
>>> http://gcc.gnu.org/ml/gcc-help/2014-03/msg00107.html
>>>
>>> the stable release version of gcc is 4.8.2.
>>> Could I get the conclusion that no one can compile it for arm platform before?
>> We have been working around this GCC 4.8 bug by disabling optimization
>> on individual compilation units.
> Would you please give us a hand about how to "disabling optimization
> on individual compilation units."
> any configure option we can use?
> or pass "-O1" instead of default "-O2" in CFLAGS?
Exactly. Compiling src/common/consumer.c,
src/common/kernel-consumer/kernel-consumer.c, and
src/common/ust-consumer/ust-consumer.c with -O1 instead of -O2 worked
for us. And if you are afraid to mess with the build system, you can
also inject
#pragma GCC optimize ("O1")
on top of those files to override the command-line optimization option.
Stefan
--
Stefan Seefeld
CodeSourcery / Mentor Embedded
http://www.mentor.com/embedded-software/
next prev parent reply other threads:[~2014-03-27 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 12:26 loody
2014-03-27 12:41 ` Stefan Seefeld
2014-03-27 12:53 ` loody
2014-03-27 12:58 ` Stefan Seefeld [this message]
2014-03-27 13:09 ` loody
2014-03-27 13:20 ` Stefan Seefeld
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=5334207E.1030007@mentor.com \
--to=stefan_seefeld@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox