-
Guest17wow
-
Guest17hello
-
br-m<rbrunner7> Does anybody happen to know whether armv7 Android is still relevant, especially for us? An AI reviewing my Polyseed PR came up with a problem of stack unwind after throw if both C and C++ code is involved, on armv7 Android if I understand correctly, and I am not sure whether this is important or not.
-
br-m<ofrnxmr:xmr.mx> cyjanek
-
br-m<ofrnxmr:xmr.mx> there are quite a few low end phones that use armv7 code on armv8 rocessors
-
br-m<ofrnxmr:xmr.mx> i think they call it like, armv8l or something like that
-
br-m<ofrnxmr:xmr.mx> grokipedia.com/page/ARMv8l
-
br-m<ofrnxmr:xmr.mx> "armv8l is the machine architecture string reported by the uname -m command in Linux when the kernel is compiled for 32-bit ARMv8 mode (AArch32) running on ARMv8-A hardware, with the "l" denoting little-endian byte orde"
-
br-m<rbrunner7> Hmm. Problem is that correcting this might not be easy. Except maybe if I can declare a single method in an otherwise C++ file to be C? ...
-
xmr-prthomasbuilds opened pull request #11257: wallet_rpc_server: reject --password with --wallet-dir
-
xmr-pr
-
xmr-prArvinFarrelP opened pull request #11259: wallet: include txid in cold-signing output export
-
xmr-pr
-
xmr-prthomasbuilds opened pull request #11258: wallet_rpc_server: reject --password with --wallet-dir [release-v0.18]
-
xmr-pr
-
br-m<jpk68:matrix.org> @rbrunner7: Considering we have release builds for it, I'd say yes.
-
selsta.merges
-
xmr-pr10886 10887 10964 10969 11054 11068 11076 11122 11123 11178 11183 11184 11191 11192 11202 11204 11205 11206 11207 11209 11212 11213 11214 11215 11217 11218
-
selsta.merge+ 11223
-
xmr-prAdded
-
xmr-prUkoeHB opened pull request #11260: wallet: pending_tx_sanity_checker followup
-
xmr-pr
-
xmr-prselsta opened pull request #11261: cryptonote_protocol: reject conflicting span reservations
-
xmr-pr
-
xmr-prselsta opened pull request #11262: device_trezor: limit protocol-v1 response length
-
xmr-pr
-
xmr-prselsta opened pull request #11263: wallet2, blockchain_ancestry: fix memory safety issues
-
xmr-pr