|
From: Feiyang C. <chr...@gm...> - 2022-08-01 02:00:47
|
Hi, I'd like to contribute code to support LOONGARCH64/Linux. Many open source projects have already supported LoongArch, such as binutils-gdb, gcc, linux kernel, glibc and so on. I am a Valgrind dev newbie and not sure how to submit patches for reviewing. I've read the git-HOWTO.txt and emails in the mailing list. Should I open a bug on the KDE Bugtracking System and attach patched to it (e.g. Bug 369509)? Thanks, Feiyang |
|
From: Mark W. <ma...@kl...> - 2022-08-01 12:21:12
|
Hi Feiyang, On Mon, 2022-08-01 at 10:00 +0800, Feiyang Chen wrote: > I'd like to contribute code to support LOONGARCH64/Linux. Many open > source projects have already supported LoongArch, such as binutils-gdb, > gcc, linux kernel, glibc and so on. I see that the upcoming glibc 2.36 release will support it. Nice. Is there a way for the community to test it? Is there qemu support? > I am a Valgrind dev newbie and not sure how to submit patches for > reviewing. I've read the git-HOWTO.txt and emails in the mailing > list. Should I open a bug on the KDE Bugtracking System and attach > patched to it (e.g. Bug 369509)? Yes, the best way would be to open a new bug and attach patches to it. We can then review those. Is there a public CPU instruction manual for the architecture? Thanks, Mark |
|
From: Feiyang C. <chr...@gm...> - 2022-08-05 02:38:10
|
Hi, Mark Thank you for your reply. On Mon, 1 Aug 2022 at 20:21, Mark Wielaard <ma...@kl...> wrote: > > Hi Feiyang, > > On Mon, 2022-08-01 at 10:00 +0800, Feiyang Chen wrote: > > I'd like to contribute code to support LOONGARCH64/Linux. Many open > > source projects have already supported LoongArch, such as binutils-gdb, > > gcc, linux kernel, glibc and so on. > > I see that the upcoming glibc 2.36 release will support it. Nice. > Is there a way for the community to test it? Is there qemu support? > I opened a bug and attached patches. Later I'll provide a 3A5000 machine for remote connection. https://bugs.kde.org/show_bug.cgi?id=457504 > > I am a Valgrind dev newbie and not sure how to submit patches for > > reviewing. I've read the git-HOWTO.txt and emails in the mailing > > list. Should I open a bug on the KDE Bugtracking System and attach > > patched to it (e.g. Bug 369509)? > > Yes, the best way would be to open a new bug and attach patches to it. > We can then review those. > > Is there a public CPU instruction manual for the architecture? > All LoongArch-related documentation can be found in this repository: https://github.com/loongson/LoongArch-Documentation Among them, the instruction manual is here: https://loongson.github.io/LoongArch-Documentation/LoongArch-Vol1-EN.html > Thanks, > > Mark Thanks, Feiyang |
|
From: Mark W. <ma...@kl...> - 2022-08-05 14:10:58
|
Hi Feiyang, On Fri, 2022-08-05 at 10:37 +0800, Feiyang Chen wrote: > I opened a bug and attached patches. Later I'll provide a 3A5000 > machine for remote connection. > > https://bugs.kde.org/show_bug.cgi?id=457504 Very nice. The test results look really good. I believe most other arches also fail drd/tests/pth_mutex_signal which indicates it is probably a broken test. You split up the support into 183 patches. Thanks. But that will take a while to review. Do things keep building for each separate patch? If not, it might make sense to merge them in groups that do and/or are logically part of the same kind of change. I will be on vacation for 2 weeks starting Monday. So my silence doesn't mean I am not interested. But hopefully someone else can take an early look at this while I am away. Cheers, Mark |
|
From: Feiyang C. <chr...@gm...> - 2022-09-08 07:59:03
|
Hi, Mark, On Fri, 5 Aug 2022 at 22:10, Mark Wielaard <ma...@kl...> wrote: > You split up the support into 183 patches. Thanks. > But that will take a while to review. Do things keep building for each > separate patch? If not, it might make sense to merge them in groups > that do and/or are logically part of the same kind of change. > I have attached patch v2 and they can keep building for each separate patch. We now have a 3A5000 desktop ready for remote connection. How can we provide it to the community? Thanks, Feiyang |