08:27:06 <m-relay> <j​effro256:monero.social> @sech1: Trying to integrate RandomX V2 in PR #10038, but the RISC-V CI build is failing when I update the RandomX submodule: https://github.com/monero-project/monero/actions/runs/22273222729/job/64431117401?pr=10038. The header `riscv_vector.h` cannot be found
08:30:55 -xmr-pr- jeffro256 opened pull request #10330: cryptonote_core: remove Boost serialization for `tx_source_entry`
08:30:55 -xmr-pr- > https://github.com/monero-project/monero/pull/10330
08:59:40 <sech1> jeffro256 you need GCC 14 for RISC-V
10:35:13 <m-relay> <r​brunner7:monero.social> Does anybody run a Monero LWS server that I could connect to for an hour or so? I would like to quickly test Skylight Wallet to check its conventional and Polyseed support, and I am lazy to compile and configure an LWS server myself just for that if I can just "borrow" somebody else's server for a while. I am also on IRC to pass me some IP in private.
10:52:38 <plowsof> rbrunner skywallet has built in tor so azefh2cpk3j2cata5gv7rlk6pflxn72lbfz6pmookgvb55pyokgphjid.onion:8443 should work unless
11:03:08 <m-relay> <r​brunner7:monero.social> Thanks a lot, plowsof, seems to work. Is this the NSA's server, or who is running that?
11:12:37 <m-relay> <o​frnxmr:xmr.mx> No, this one is the nsa migfi5a4d4x5fupdvtxbl4azrfxtuhjogjuo63tbjekcjqfkqmgbhlid.onion:18086
11:16:34 <m-relay> <r​brunner7:monero.social> Hmm, the first address gives me a connection error while in the newly created wallet, but never mind, I can make my tests
11:18:37 <m-relay> <o​frnxmr:xmr.mx> What sort of error? On what screen? Lws likes to connect & disconnect repeatedly
11:20:28 <m-relay> <r​brunner7:monero.social> In the wallet display, topleft corner, onion icon with red cross, and giving me a tooltip of "Failed to connect to ..."
11:21:04 <m-relay> <r​brunner7:monero.social> Tor connectivity is built-in, right, I don't have to connect myself "manually" to Tor first?
11:22:04 <m-relay> <o​frnxmr:xmr.mx> correct, if using built-in tor, it starts rhe daemon at wallet open
11:23:09 <m-relay> <r​brunner7:monero.social> Oh, for a wallet restore, it won't let me past the Tor config screen, with connection error. Sigh.
11:24:17 <m-relay> <r​brunner7:monero.social> Never mind, the second address works right now
12:59:08 <plowsof> rbrunner not an nsa server, ghcq 
13:01:15 <m-relay> <r​brunner7:monero.social> Sure :) Still pretty basic, that Skylight wallet app.
13:04:31 <tobtoht> .merges
13:04:31 -xmr-pr- 10161 10162 10299 10312 10314 10315 10316 10317 10318 10319 10320
13:04:40 <tobtoht> oh still borked
13:04:45 <tobtoht> anyway, done
13:20:21 <selsta> it recognises new PRs being opened so my IP is not banned.. will have to check if logs exist later today
13:36:23 <plowsof> rbrunner : you crashed it :( cc ofrnxmr https://paste.debian.net/hidden/d41290d8
13:37:42 <m-relay> <r​brunner7:monero.social> Cool
13:41:34 <m-relay> <o​frnxmr:monero.social> Plowsof, are you running latest version?
13:42:28 <m-relay> <o​frnxmr:monero.social> I havent seen that bug myself, but i run bleeding edge (develop branch) that has a lot of bugs fixed
13:43:34 <plowsof> ghcr.io/vtnerd/monero-lws:latest (docker :( )
14:00:55 -xmr-pr- tobtoht opened pull request #10331: guix: bump time-machine to 4a507aa8c0a579d150267d81ab4013189a7ec505
14:00:55 -xmr-pr- > https://github.com/monero-project/monero/pull/10331
15:32:05 <m-relay> <o​frnxmr:xmr.mx> So either master or release?
15:37:54 <m-relay> <o​frnxmr:xmr.mx> the branches dont seem that far off. Cc vtnerd
15:38:00 <m-relay> <o​frnxmr:xmr.mx> ^
16:21:01 <m-relay> <r​brunner7:monero.social> Just for the record: I just created a few new wallets in the latest version of Skylight wallet app, and restored a few from seed. No transactions whatsoever. Deleted wallets, to be able to create new ones, because of the missing handling of wallets by filename.
18:28:02 <m-relay> <v​tnerd:monero.social> I think this is an outdated version as the line number doesn't map to anything on 0.3 master or develop
18:36:08 <m-relay> <j​effro256:monero.social> sech1: Would it be possible to implement a fallback? Right now the minimum GCC version for Monero is 7, released in 2017. Bumping to GCC 14, released in 2024, would require a 7-year leap forward in our primary dependency.
18:39:07 <m-relay> <o​frnxmr:xmr.mx> On master?
18:39:40 <m-relay> <v​tnerd:monero.social> Master requires c++17 which was enabled by default in gcc 11
18:40:02 <m-relay> <v​tnerd:monero.social> So even then it's a bump forward from min requirements
18:43:04 <m-relay> <o​frnxmr:xmr.mx> I think 7 is release because we build with (EOL'd) 18.04. But yeah, 14 isnt available on ubuntu til 24.04
18:43:19 <m-relay> <o​frnxmr:xmr.mx> https://documentation.ubuntu.com/ubuntu-for-developers/reference/availability/gcc/
18:44:43 <sech1> jeffro256 this is only for riscv builds
18:45:18 <sech1> riscv is a relatively new platform, especially the vector extensions, so no way around that
18:47:55 <m-relay> <j​effro256:monero.social> GCC 7.x contains full support for C++17 as long as you pass `-std=c++17` to the compiler, which we do, so we don't effectively need GCC 11 as the minimum requirement AFAIK
18:48:23 <sech1> gcc 7 knows nothing about riscv though
18:48:27 <sech1> as I said, it's a new platform
18:49:05 <sech1> basically all recent risc-v boards have gcc 15
18:49:42 <m-relay> <j​effro256:monero.social> sech1: yes I understand, but can't you use conditional compilation to fallback to an interpreted VM when vector intrinsics aren't supported by the current compiler?
18:50:30 <m-relay> <j​effro256:monero.social> Or are you saying that standard C++ won't compile for RISC-V on GCC 7?
18:51:29 <m-relay> <o​frnxmr:xmr.mx> https://github.com/monero-project/monero/pull/9448#issuecomment-2306893632
18:51:42 <m-relay> <o​frnxmr:xmr.mx> >  building master with 7 is broken.
18:52:28 <m-relay> <o​frnxmr:xmr.mx> (possibly outdated comment)
18:52:35 <sech1> gcc 7 is ancient
18:53:16 <sech1> Why we don't build official release builds using the latest and greatest versions of GCC, is beyond me
18:54:13 <sech1> And why should I add more #ifdefs and cmake file edits just to support ancient compilers for platform that doesn't even have these ancient compilers
18:54:26 <sech1> find me any riscv board that has anything older than gcc 14
18:55:04 <m-relay> <o​frnxmr:xmr.mx> sech1 because they are built with gitian, which is using ancient EOL'd 18.04
18:55:21 <sech1> there is a PR for guix builds
18:55:30 <sech1> it updated riscv build to use gcc 14, that's it
18:55:35 <sech1> no more things needed to do here
18:56:08 <m-relay> <o​frnxmr:xmr.mx> guix builds are for master
18:56:30 <m-relay> <o​frnxmr:xmr.mx> so if we branch from master (which we all want to) then were good
18:56:37 <sech1> yes, and randomx v2 (that has this code) is also for master
18:58:04 <sech1> https://github.com/monero-project/monero/pull/9969
18:58:33 <m-relay> <o​frnxmr:xmr.mx> Also, fcmp runs like trash on old rust versions, so i dont think we should cripple the software bt supporting inefficient or ancient libs at this hard fork
19:09:40 <m-relay> <j​effro256:monero.social> sech1: just because we use GCC14 for GUIX doesn't automatically mean that we shouldn't support lower versions of GCC for other compilation pathways IMO
19:11:31 <m-relay> <0​xfffc:monero.social> Any plan for C++20?
19:11:38 <sech1> Then there will be no vector code for RandomX (even the original one) on RISC-V platform
19:11:50 <sech1> And hash verification will be 30% slower
19:12:13 <sech1> jeffro256 lower versions of GCC are supported, just not for RISC-V
19:13:24 <sech1> RISC-V RVA23 makes them mandatory, so all future boards must support vector extensions, which means they _must_ ship gcc 14 or newer
19:13:57 <sech1> Again, I don't see a point to support anything older on RISC-V
19:15:39 <m-relay> <s​yntheticbird:monero.social> I love it when a C++ codebase upgrade to a new C++ feature set version but there is no one motivated into improving the existing parts of the codebase with the new feature set
19:20:05 <sech1> Maybe because "if it works - don't touch it" rule...
19:22:19 <m-relay> <s​yntheticbird:monero.social> right
19:22:32 <m-relay> <s​yntheticbird:monero.social> so there is really no reason to upgrade the C++ version in an already mature project
19:24:06 <m-relay> <s​yntheticbird:monero.social> beside me ragebaiting, 0xfffc what exactly does C++20 would bring ?
20:37:55 <sech1> It makes sense to upgrade to use new features in the new code