From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] libsoup-2.4: upgrade to 2.45.92
Date: Tue, 25 Mar 2014 12:12:55 +0800 [thread overview]
Message-ID: <53310247.3080001@windriver.com> (raw)
In-Reply-To: <CAJTo0LY2rkPew8354+pYJKjXSrsBa50kZeEwxDrXSnQWgi8gRw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On 03/24/2014 05:06 PM, Burton, Ross wrote:
> On 24 March 2014 07:57, Hongxu Jia <hongxu.jia@windriver.com> wrote:
>> There was an error about mips-gcc optimization while compiling
>> libsoup-2.4 2.45.3 with DEBUG_OPTIMIZATION enabled.
>>
>> The test code of libsoup-2.4 2.45.3 triggered gcc assert which located
>> in gcc/dwarf2out.c:20810:
>> ...
>> 20806 gcc_assert (prev
>> 20807 && (CALL_P (prev)
>> 20808 || (NONJUMP_INSN_P (prev)
>> 20809 && GET_CODE (PATTERN (prev)) == SEQUENCE
>> 20810 && CALL_P (XVECEXP (PATTERN (prev), 0,
>> 0)))));
>> ...
> So you've a bug in gcc and a well defined way of replicating it,
> presumably you've reported this to gcc as that's the proper fix here?
Yes, file a bug in gcc:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6034
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60643
//Hongxu
> Ross
[-- Attachment #2: Type: text/html, Size: 2046 bytes --]
next prev parent reply other threads:[~2014-03-25 4:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 7:40 [PATCH 0/1] libsoup-2.4: upgrade to 2.45.92 Hongxu Jia
2014-03-24 7:40 ` [PATCH 1/1] " Hongxu Jia
2014-03-24 7:57 ` Hongxu Jia
2014-03-24 9:06 ` Burton, Ross
2014-03-25 4:12 ` Hongxu Jia [this message]
2014-03-24 8:09 ` Burton, Ross
2014-03-24 8:15 ` Hongxu Jia
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=53310247.3080001@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.