From: Wei Huang <w1.huang@samsung.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Stefano Stabellini (Xen mainlister)"
<stefano.stabellini@eu.citrix.com>, duqi <duqi_2009@163.com>,
"Julien Grall" <julien.grall@linaro.org>, 宫晓利 <nkgongxl@163.com>,
hdegoede <hdegoede@redhat.com>,
"bjzhang@suse.com" <bjzhang@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: The segmentfault when using xl create domU
Date: Wed, 16 Apr 2014 10:50:50 -0500 [thread overview]
Message-ID: <534EA6DA.3020301@samsung.com> (raw)
In-Reply-To: <1397640079.24638.134.camel@kazak.uk.xensource.com>
On 04/16/2014 04:21 AM, Ian Campbell wrote:
> On Tue, 2014-04-15 at 17:07 -0500, Wei Huang wrote:
>>> It's a compiler bug. For some reasons gcc doesn't generate the right assembly
>>> when -O1 is specified on the command line. Which version of gcc do you use(4.7.*?)?
>>> Which distribution are you using?
>>> Can you also call disas the crash and copy the output?
>>>
>>> Gcc 4.8 doesn't seem to be affected.
>>>
>>> FYI, I got this output from 4.7 with Linaro Ubuntu raring (gcc 4.7.3).
>>> [...]
>> I saw the same thing on my system and ack'ed that this is compiler
>> related. My compiler is 4.7.3. I was able to fix it with the following hack:
>
> Are you also using the Linaro compiler by any chance?
I think so. Here is the GCC --version info:
arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3
>
> I've added warnings to
> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling
> and
> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions#Building_Xen_on_ARM
>
>
next prev parent reply other threads:[~2014-04-16 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 2:33 The segmentfault when using xl create domU duqi
2014-04-15 8:53 ` Ian Campbell
2014-04-15 9:45 ` duqi
2014-04-15 14:12 ` Julien Grall
2014-04-15 22:07 ` Wei Huang
2014-04-16 9:21 ` Ian Campbell
2014-04-16 15:50 ` Wei Huang [this message]
2014-04-16 15:56 ` Julien Grall
2014-04-16 9:12 ` duqi
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=534EA6DA.3020301@samsung.com \
--to=w1.huang@samsung.com \
--cc=Ian.Campbell@citrix.com \
--cc=bjzhang@suse.com \
--cc=duqi_2009@163.com \
--cc=hdegoede@redhat.com \
--cc=julien.grall@linaro.org \
--cc=nkgongxl@163.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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.