From: Julien Grall <julien.grall@linaro.org>
To: Wei Huang <w1.huang@samsung.com>
Cc: "Ian Campbell" <Ian.Campbell@citrix.com>,
"Stefano Stabellini (Xen mainlister)"
<stefano.stabellini@eu.citrix.com>, duqi <duqi_2009@163.com>,
宫晓利 <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 16:56:17 +0100 [thread overview]
Message-ID: <534EA821.7060702@linaro.org> (raw)
In-Reply-To: <534EA6DA.3020301@samsung.com>
On 04/16/2014 04:50 PM, Wei Huang wrote:
> 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
Linaro as shipped a new version of GCC 4.7 (based on 4.7.4) a couple of
days ago.
They don't plan to release another version of 4.7. So I don't think it's
useful to report the bug. Unless it's also happen with upstream GCC.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-04-16 15:56 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
2014-04-16 15:56 ` Julien Grall [this message]
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=534EA821.7060702@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=bjzhang@suse.com \
--cc=duqi_2009@163.com \
--cc=hdegoede@redhat.com \
--cc=nkgongxl@163.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=w1.huang@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).