Delivery-date: Thu, 21 Nov 2024 16:07:48 -0800
Sender: bitcoindev@googlegroups.com
Date: Thu, 21 Nov 2024 15:57:35 -0800 (PST)
From: Antoine Riard <antoine.riard@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <db8e3abd-7247-41be-ab97-71d20c2f775cn@googlegroups.com>
In-Reply-To: <e5b06aaa-1fe9-4c8f-a0ea-db10f8a7e48cn@googlegroups.com>
References: <e5b06aaa-1fe9-4c8f-a0ea-db10f8a7e48cn@googlegroups.com>
Subject: [bitcoindev] Re: Bitcoin Core on ARM (Windows)
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_75496_1298159466.1732233455552"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_75496_1298159466.1732233455552
Content-Type: multipart/alternative; 
	boundary="----=_Part_75497_948288349.1732233455552"

------=_Part_75497_948288349.1732233455552
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Ali,

For the process of compiling Windows on the ARM instruction set=20
architecture it's about
instructing your compiler (e.g gcc or clang) to build your kernel code for=
=20
the correct
CPU / hardware platform. There is no ARM toolchain per se, modern compilers=
=20
can do well
cross-platform compilation (at least building on x86-64 and targeting ARM).=
=20
Then it's
a bit of linker magic.

About the usage of x86-specific assembly functions in the bitcoin core=20
codebase, I think
there are some in the secp256k1 library about some scalar optimizations.

That might interest you:=20
https://groups.google.com/g/bitcoindev/c/fOIByS6COMk It's less
about compiling the whole machinery of bitcoin core itself and more focus=
=20
on the libbitcoinkernel
engine, though including RISC-V support for the consensus engine=20
compilation would be a
significant improvement, imho.

Best,
Antoine
ots hash: d507461412e46e21156e9e2de5d65584c27d0cbca75d2e810f514fe8e077c9bd
Le jeudi 21 novembre 2024 =C3=A0 09:04:26 UTC, Ali Sherief a =C3=A9crit :

> Apparently, there are only ARM binaries for Linux but not for Windows.
>
> Considering that Apple Silicon is basically ARM as well, that means ARM=
=20
> binaries are produced for all the major operating systems except for=20
> Windows.
>
> What would the process of compiling Windows with the ARM toolchain look=
=20
> like? Do any of these methods have Arm64 support?
>
> > On Linux, using the Mingw-w64 cross compiler tool chain.
> > On Windows, using Windows Subsystem for Linux (WSL) and Mingw-w64.
> > On Windows, using Microsoft Visual Studio. See build-windows-msvc.md.
>
> These are from the Windows build guide by the way.
>
> I suppose Visual Studio might support ARM, but perhaps there are some=20
> x86-specific assembly functions used inside the codebase which might make=
=20
> it difficult to build.
>
> - Ali
>

--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
db8e3abd-7247-41be-ab97-71d20c2f775cn%40googlegroups.com.

------=_Part_75497_948288349.1732233455552
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Ali,<br /><br />For the process of compiling Windows on the ARM instruct=
ion set architecture it's about<br />instructing your compiler (e.g gcc or =
clang) to build your kernel code for the correct<br />CPU / hardware platfo=
rm. There is no ARM toolchain per se, modern compilers can do well<br />cro=
ss-platform compilation (at least building on x86-64 and targeting ARM). Th=
en it's<br />a bit of linker magic.<br /><br />About the usage of x86-speci=
fic assembly functions in the bitcoin core codebase, I think<br />there are=
 some in the secp256k1 library about some scalar optimizations.<br /><br />=
That might interest you: https://groups.google.com/g/bitcoindev/c/fOIByS6CO=
Mk It's less<div>about compiling the whole machinery of bitcoin core itself=
 and more focus on the libbitcoinkernel</div><div>engine, though including =
RISC-V support for the consensus engine compilation would be a</div><div>si=
gnificant improvement, imho.<br /><br />Best,<br />Antoine<br />ots hash: d=
507461412e46e21156e9e2de5d65584c27d0cbca75d2e810f514fe8e077c9bd<br /></div>=
<div class=3D"gmail_quote"><div dir=3D"auto" class=3D"gmail_attr">Le jeudi =
21 novembre 2024 =C3=A0 09:04:26 UTC, Ali Sherief a =C3=A9crit=C2=A0:<br/><=
/div><blockquote class=3D"gmail_quote" style=3D"margin: 0 0 0 0.8ex; border=
-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Apparently, there =
are only ARM binaries for Linux but not for Windows.<div><br></div><div>Con=
sidering that Apple Silicon is basically ARM as well, that means ARM binari=
es are produced for all the major operating systems except for Windows.</di=
v><div><br></div><div>What would the process of compiling Windows with the =
ARM toolchain look like? Do any of these methods have Arm64 support?</div><=
div><br></div><div>&gt; On Linux, using the Mingw-w64 cross compiler tool c=
hain.</div>&gt; On Windows, using Windows Subsystem for Linux (WSL) and Min=
gw-w64.<br>&gt; On Windows, using Microsoft Visual Studio. See build-window=
s-msvc.md.<div><br></div><div>These are from the Windows build guide by the=
 way.</div><div><br></div><div>I suppose Visual Studio might support ARM, b=
ut perhaps there are some x86-specific assembly functions used inside the c=
odebase which might make it difficult to build.</div><div><br></div><div>- =
Ali</div></blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/db8e3abd-7247-41be-ab97-71d20c2f775cn%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/db8e3abd-7247-41be-ab97-71d20c2f775cn%40googlegroups.com</a>.<br />

------=_Part_75497_948288349.1732233455552--

------=_Part_75496_1298159466.1732233455552--