mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jinyang He <hejinyang@loongson.cn>
To: Youling Tang <tangyouling@loongson.cn>, Xi Ruoyao <xry111@xry111.site>
Cc: loongarch@lists.linux.dev, Huacai Chen <chenhuacai@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>,
	linux-kernel@vger.kernel.org
Subject: Re: "kernel ade access" oops on LoongArch
Date: Wed, 15 Feb 2023 15:51:46 +0800	[thread overview]
Message-ID: <5403e5eb-5792-7d6f-df74-ca3fab82ecd5@loongson.cn> (raw)
In-Reply-To: <9a70e89c-0f3b-0660-501e-3292e410cfd8@loongson.cn>

On 2023-02-15 15:23, Youling Tang wrote:

>
>
> On 02/15/2023 01:35 PM, Xi Ruoyao wrote:
>> On Wed, 2023-02-15 at 12:52 +0800, Youling Tang wrote:
>>> ../stdlib/stdlib.h:141:8: error: ‘_Float32’ does not name a type
>>>    141 | extern _Float32 strtof32 (const char *__restrict __nptr,
>>>        |        ^~~~~~~~
>>
>> This is because Glibc expects GCC 13 to support _Float32, but early GCC
>> 13 snapshots did not.
>>
>>> /usr/bin/ld: /home/loongson/build_glibc/libc.a(dl-reloc-static-pie.o):
>>> in function `_dl_relocate_static_pie':
>>> /home/loongson/glibc/elf/dl-reloc-static-pie.c:44: undefined reference
>>> to `_DYNAMIC'
>>
>> Oh, this one is my fault.  The check for compiler static PIE support was
>> not written correctly.  I'll fix it for Glibc later, but now you can
>> update GCC to the latest git master to proceed.
>>
>
> Tested on Loongson-3C5000L-LL machine, using CLFS7.3 system.
>
> $ gcc -v
> gcc version 13.0.0 20221018 (experimental) (GCC)
>
> # make check -j32
> /home/loongson/build_glibc/math/test-tgmath3-atan2.c: 
> 在函数‘test_atan2_84’中:
> /home/loongson/build_glibc/math/test-tgmath3-atan2.c:903:59: 
> 错误:conflicting types for ‘var__Float32x’; have ‘double’
>   903 |   extern typeof (atan2 (vol_var__Float32x, vol_var_char)) 
> var__Float32x __attribute__ ((unused));
>       | ^~~~~~~~~~~~~
>
> There was a build error in make check, so only tst-mallocfork3-
> malloc-check was tested separately.
>
> # make test t=malloc/tst-mallocfork3-malloc-check
> make[2]: 离开目录“/home/loongson/glibc/malloc”
> PASS: malloc/tst-mallocfork3-malloc-check
> original exit status 0
> info: signals received during fork: 301
> info: signals received during free: 1693
> info: signals received during malloc: 119
> make[1]: 离开目录“/home/loongson/glibc”
>
> A total of five tests are PASS, and the serial port does not display
> CallTrace.
>
> Youling.
>
I had test it by using the cmd "while true..." Ruoyao gave on

Loongson-3A5000, CLFS 7.1, 6.2-rc8 kernel with those patches and

6.2-rc7 kernel form loongson-next. No calltrace displayed, either.

Jinyang


  reply	other threads:[~2023-02-15  7:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  8:46 Xi Ruoyao
2023-02-14 14:51 ` Huacai Chen
2023-02-15  4:52 ` Youling Tang
2023-02-15  5:35   ` Xi Ruoyao
2023-02-15  7:23     ` Youling Tang
2023-02-15  7:51       ` Jinyang He [this message]
2023-02-15  8:07         ` Xi Ruoyao
2023-02-15  8:25           ` Youling Tang
2023-02-15  8:35             ` Xi Ruoyao
2023-02-15 11:52               ` Xi Ruoyao
2023-02-15 12:51                 ` Xi Ruoyao
2023-02-15 13:06                   ` Xi Ruoyao

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=5403e5eb-5792-7d6f-df74-ca3fab82ecd5@loongson.cn \
    --to=hejinyang@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=tangyouling@loongson.cn \
    --cc=xry111@xry111.site \
    /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

all inboxes | Powered by JetHome®