2025-03-10 16:34:23 <ncopa> the build of linux-lts 6.12.18 failed on loongarch: error: implicit declaration of function 'annotate_reachable'
2025-03-10 16:34:30 <ncopa> anyonly has time to help with that?
2025-03-10 16:34:45 <ncopa> <@ikke> Probably caused by https://lore.kernel.org/all/20250305174506.868421566@linuxfoundation.org/
2025-03-10 16:35:06 <ncopa> i suppose we could just add a revert commit of that
2025-03-10 16:36:02 <ncopa> or maybe not...
2025-03-10 16:36:21 <ncopa> commit message says:
2025-03-10 16:36:24 <ncopa> And the annotate_unreachable() usage in unreachable() is plain wrong;
2025-03-10 16:36:24 <ncopa> it will hide dangerous fall-through code-gen.
2025-03-10 17:28:31 <fossdd[m]> there are other patches in the series (https://lore.kernel.org/all/20241128094312.235637588@infradead.org/), maybe the backported patch depends on one
2025-03-10 17:44:16 <fossdd[m]> https://lore.kernel.org/all/20241128094312.133437051@infradead.org/ should fix it
2025-03-10 18:02:57 <fossdd[m]> ncopa: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/81128
2025-03-10 18:03:35 <fossdd[m]> is also already queued for 6.12.19: https://lore.kernel.org/stable/20250310170458.155042546@linuxfoundation.org/
2025-03-10 19:22:57 <ncopa> thanks!
2025-03-11 00:50:45 <huajingyun> Good morning!
2025-03-11 00:51:14 <huajingyun> Thanks ncopa fossdd[m]
2025-03-11 08:54:05 <mps> ncopa: same happens with kernel 6.13.6
2025-03-11 09:37:26 <huajingyun> Yeah, the patch mentioned by fossdd[m] can be used as a fix. https://lore.kernel.org/all/20241128094312.235637588@infradead.org/
2025-03-11 09:41:26 <huajingyun> https://lore.kernel.org/loongarch/20250309195622.1541936-1-ojeda@kernel.org/T/#t
2025-03-11 10:07:09 <mps> https://lore.kernel.org/all/20250310170447.729440535@linuxfoundation.org
2025-03-11 10:07:20 <mps> huajingyun: ^
2025-03-11 10:07:50 <mps> 6.13.7rc1
2025-03-13 10:55:43 <mps> In file included from /home/mps/aports/community/telegram-desktop/src/tdesktop-5.12.4-full/Telegram/lib_webview/webview/webview_dialog.cpp:13:
2025-03-13 10:55:46 <mps> /home/mps/aports/community/telegram-desktop/src/tdesktop-5.12.4-full/Telegram/lib_ui/ui/widgets/buttons.h:276:17: error: 'nullptr_t' has not been declared
2025-03-13 10:55:49 <mps>   276 |                 nullptr_t,
2025-03-13 10:55:52 <mps>       |                 ^~~~~~~~~
2025-03-13 10:55:54 <mps> ninja: subcommand failed
2025-03-13 10:56:22 <mps> what should be included to fix this
2025-03-13 10:56:52 <mps> which file i mean
2025-03-13 12:12:50 <huajingyun> Maybe need to add  #include <cstddef> in Telegram/lib_ui/ui/widgets/buttons.h
2025-03-13 12:19:01 <huajingyun> Aha, same error on x86_64
2025-03-13 12:19:47 <mps> yes, error is on all arches
2025-03-13 12:26:15 <mps> #include <cstddef> didn't helped
2025-03-13 12:26:23 <huajingyun> The following changes seem to work:
2025-03-13 12:26:23 <huajingyun> 2. Change nullptr_t to std::nullptr_t in Telegram/lib_ui/ui/widgets/buttons.cpp,
2025-03-13 12:26:23 <huajingyun> 1. Add #include <cstddef> in Telegram/lib_ui/ui/widgets/buttons.h and change nullptr_t to std::nullptr_t,
2025-03-13 12:26:49 <mps> ok, will try
2025-03-13 12:26:51 <huajingyun> Do you have time to try it?
2025-03-13 12:27:01 <huajingyun> ok
2025-03-13 12:31:24 <mps> 
ACTION wonders why i take to maintain any pkg written in C++

2025-03-13 12:32:46 <mps> also above don't work. nvm, it is not important to upgrade tdesktop
2025-03-13 12:34:46 <mps> and i don't understand C++ nor its namespace
2025-03-13 12:37:47 <huajingyun> Well, I'm not sure, but let me try
2025-03-13 12:39:55 <mps> i will try again on clean source tree
2025-03-13 12:42:32 <mps> huajingyun: looks like it works
2025-03-13 12:42:41 <mps> thanks
2025-03-13 12:43:36 <mps> i will try on aarch64 also to if binary work
2025-03-13 12:48:27 <huajingyun> Ok, you're welcome
2025-03-13 12:53:19 <huajingyun> Wonder why there is an error on alpine, maybe g++ is different in some places
2025-03-13 12:55:34 <huajingyun> mps: I'll be going AFK soon,hopefully binary will work too
2025-03-13 12:55:53 <huajingyun> Bye
2025-03-13 12:56:18 <mps> huajingyun: thanks, i will report here later
2025-03-13 16:46:04 <mps> kernel 6.13.7 builds on loongarch64. i guess also 6.12.19 will
2025-03-13 16:48:38 <mps> huajingyun: telegram-desktop works with your proposed fixes. diff is here https://tpaste.us/Kx0o
2025-03-14 01:09:34 <huajingyun> mps:That's good,thanks for telling me:)
2025-03-14 06:33:10 <mps> huajingyun: np, you found fix, thanks again
2025-03-14 06:43:33 <huajingyun> You're welcome:)
2025-03-17 00:16:19 <jvvv> i'm preparing an upgrade for gutenprint. the new release has a more recent config.sub and the current aport updates this. the most probable issue i see is the lack of loongarchx32 in the new config.sub in the source. doen't seem to me that this should pose a problem, but maybe someone here knows better.
2025-03-17 00:23:55 <jvvv> here is the diff between the abuild config.sub and the new one in the source: https://tpaste.us/1yBQ
2025-03-17 01:32:52 <huajingyun> jvvv: Yeah, since the updated config.sub is already supported in the new gutenprint release, I think "update_config_sub" in gutenprint aports can be removed
2025-03-17 01:53:16 <DWwanghao> Yes, the latest 5.3.5 release source code is already compatible; update_config_sub has become redundant after the upgrade and can be removed.
2025-03-17 02:39:46 <mio> community/miller test seems to be failing at the moment on loongarch64, has anyone come across this before? https://build.alpinelinux.org/buildlogs/build-edge-loongarch64/community/miller/miller-6.13.0-r3.log
2025-03-17 02:41:31 <mio> it passed on other arches
2025-03-17 02:44:34 <mio> (it came up during a rebuild with go 1.24.1)
2025-03-17 02:58:33 <huajingyun> DWwanghao: Do you have time to look at community/miller?
2025-03-17 03:06:11 <DWwanghao> huajingyun:Yach, I'm looking into it.
2025-03-17 03:08:36 <huajingyun> Thanks
2025-03-17 03:09:27 <mio> thanks!
2025-03-17 03:39:59 <DWwanghao> mio:It appears to be a precision issue in floating-point calculations. I have already reported it to the LoongArch Go compiler team,
2025-03-17 03:40:14 <DWwanghao>  and I will continue to follow up. I will provide you with an update once there are any results.
2025-03-17 03:40:52 <mio> DWwanghao: thanks for the quick reply and diagnosis!
2025-03-17 03:41:12 <DWwanghao> You're welcome:)
2025-03-17 03:41:50 <mio> :)
2025-03-17 22:09:35 <Ariadne> in some cases (such as viewing PDFs), i am seeing graphical corruption in firefox on loongarch.  the nature of the graphical corruption i am seeing indicates to me that some image tiles are 2x wider than they should be
2025-03-17 22:09:56 <Ariadne> how vetted is some of this LASX code?
2025-03-17 22:16:13 <Ariadne> example of corruption https://usercontent.irccloud-cdn.com/file/V9MKaVdC/Screenshot_20250317_151548.png
2025-03-17 22:29:20 <Ariadne> correction, that actually looks like it is 4x wider than it should be
2025-03-17 22:29:37 <Ariadne> which reinforces the likelihood that this is a vectorization issue
2025-03-17 22:30:02 <Ariadne> (4bpc vs 1bpc for 32-bit color)
2025-03-17 22:43:24 <Ariadne> you can also download the original PDF here: https://rippling2.imgix.net/Complaint.pdf it's a great read despite the graphics corruption
2025-03-17 22:59:17 <ptrc> hm, not sure which patch could be responsible for this
2025-03-17 23:00:44 <ptrc> though as far as i can tell, both larger lasx patches were at some point touched by me
2025-03-17 23:00:50 <ptrc> so it's probably something i broke
2025-03-17 23:01:03 <ptrc> is there a reliable way to emulate loong64 on amd64
2025-03-17 23:12:35 <Ariadne> this smells like it is in Skia
2025-03-17 23:29:38 <Ariadne> i don't think it is any edits you've made, tab previews have had similar graphical corruption since day 1 for me.  i just don't care about tab previews
2025-03-17 23:51:20 <Ariadne> digging further, it appears the corrupted images are PNGs
2025-03-18 00:02:24 <Ariadne> hmm, no.  they are all jpegs according to my copy of acrobat
2025-03-18 00:02:33 <Ariadne> BUT they are being resized with a mask
2025-03-18 00:02:50 <Ariadne> i am blaming skia here
2025-03-18 04:49:15 <mio> DWwanghao: discussed the situation of miller with miller's maintainer, will temporarily skip the test cases to unblock the builder. it would be still be great if there's an update or fix, whenever it happens
2025-03-18 04:51:37 <xen0n> Ariadne: I've noticed the same before on Gentoo, but I gather some other distros do not have this problem
2025-03-18 04:52:27 <Ariadne> i’m almost certain something is wrong in skia
2025-03-18 04:52:28 <xen0n> I'll try to debug in a few days or maybe 2 weeks, it's most likely Skia but miscompilation could also be a problem
2025-03-18 04:53:11 <Ariadne> it seems like it is effectively 4x’ing row-stride.  i used to see this with altivec code a lot back in the day.
2025-03-18 04:53:18 <xen0n> yeah, I've tried to pinpoint the issue but the Skia test suite (dm) doesn't expose the problem
2025-03-18 04:53:52 <Ariadne> one option to verify the theory might be to build skia with the vector code disabled
2025-03-18 04:54:05 <xen0n> during my work on https://skia-review.googlesource.com/c/skia/+/908137 I compared the results on loongarch64 with amd64 and they're mostly the same
2025-03-18 04:54:30 <xen0n> wrt disabling SIMD, you're right, I didn't test this
2025-03-18 04:54:52 <xen0n> thanks for the tip, I'll try it shortly and see ;-)
2025-03-18 04:56:06 <Ariadne> unrelated: strangely the entirety of firefox segfaults if i try to configure a lenovo t14s in the lenovo store website
2025-03-18 04:56:26 <Ariadne> will try to get a backtrace
2025-03-18 05:02:20 <huajingyun1> I created a mr to fix hugo test failure on loongarch64 !81502
2025-03-18 05:05:20 <huajingyun1> it would be great if someone is willing to help merge it. The builder is also blocked by hugo
2025-03-18 05:08:21 <Ariadne> CI failure?
2025-03-18 05:42:15 <Ariadne> merged
2025-03-18 06:04:08 <huajingyun1> Ariadne: thanks!
2025-03-18 07:21:41 <ncopa> thanks for fixing hugo!
2025-03-18 07:34:28 <huajingyun1> Hi, ncopa, you’re welcome!
2025-03-18 07:36:53 <huajingyun1> Thanks also to Ariadne for helping with the timely merge
2025-03-18 07:38:51 <DWwanghao> mio:Okay, any further fixes or updates will be posted in the IRC in a timely manner.
2025-03-18 07:38:58 <DWwanghao> Thank you for your help in keeping the build server running.
2025-03-18 13:02:08 <mio> DWwanghao: great, thanks for following up on the progress