From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Khem Raj <raj.khem@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: OE-Core status with gcc9
Date: Thu, 6 Jun 2019 16:16:27 +0800 [thread overview]
Message-ID: <5CF8CBDB.8010705@windriver.com> (raw)
In-Reply-To: <CAMKF1soM4-qnt9STcuV=e8T=zLx1ESR=0HT3xeCCJ4J7mxCc_w@mail.gmail.com>
On 2019年05月27日 15:53, Khem Raj wrote:
> On Sun, May 26, 2019 at 10:17 AM Khem Raj <raj.khem@gmail.com> wrote:
>>
>> On Mon, May 13, 2019 at 8:39 PM Khem Raj <raj.khem@gmail.com> wrote:
>>>
>>> On Sun, May 12, 2019 at 1:14 PM Khem Raj <raj.khem@gmail.com> wrote:
>>>>
>>>> On Sun, May 12, 2019 at 6:21 AM Richard Purdie
>>>> <richard.purdie@linuxfoundation.org> wrote:
>>>>>
>>>>> I've run some tests and think we're now down to one remaining issue
>>>>> with gcc 9:
>>>>>
>>>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/579
>>>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/55/builds/145
>>>>>
>>>>
>>>> Assembler is not liking what gcc9 is generating
>>>>
>>>> HOSTCC scripts/kconfig/conf.o
>>>> /tmp/ccnMW5be.s: Assembler messages:
>>>> /tmp/ccnMW5be.s: Internal error (Segmentation fault).
>>>>
>>>> I wonder if its a common case or specific here?
>>>> I will try to reproduce it as well
>>>>
>>>
>>> I am able to get a .s file which crashes assembler on
>>> qemu. Same file assembles ok with mips cross assembler
>>> so next I want to get hold of a mips hardware and try
>>> it on the real h/w, meanwhile if someone has easy access
>>> to mips and can load core-image-sato-sdk on it then I can
>>> provide the asm file which crashes assembler
>>>
>> got some more time to narrow it down.
>> works with musl+gcc-9
>> works with glibc+clang-8
>> works with musl+Clang-8
>>
>> so only glibc+gcc-9 combo is one which exhibits the issue
>>
>
> I have sent a workaound for this which we can try out.
> https://patchwork.openembedded.org/patch/161674/
Failed to build llvm with gcc9 for qemuppc as below:
| collect2: fatal error: ld terminated with signal 11 [Segmentation
fault], core dumped
Thanks,
>
>>>>> which is a kernel "make scripts" segfaulting on target on mips and
>>>>> hence failing to build kernel modules. If we can get that one fixed
>>>>> we're good from an OE-Core perspective to move to gcc 9.
>>>>>
>>>>> I have to recognise the work Khem has put in getting us this close!
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Richard
>>>>>
next prev parent reply other threads:[~2019-06-06 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 13:21 OE-Core status with gcc9 Richard Purdie
2019-05-12 17:14 ` Khem Raj
2019-05-14 3:39 ` Khem Raj
2019-05-26 17:17 ` Khem Raj
2019-05-27 7:53 ` Khem Raj
2019-06-06 8:16 ` Yu, Mingli [this message]
2019-06-06 12:55 ` nick83ola
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=5CF8CBDB.8010705@windriver.com \
--to=mingli.yu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.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