On Nov 27 08:47, Jeremy Drake via Cygwin-patches wrote:
> On Wed, 27 Nov 2024, Corinna Vinschen wrote:
>
> > I'm not opposed to a switch statement consisting of an
> > IMAGE_FILE_MACHINE_ARM64 case and a default case adding "-???" or
> > something. Chances are so extremly slim that we'll ever see
On Wed, 27 Nov 2024, Corinna Vinschen wrote:
> I'm not opposed to a switch statement consisting of an
> IMAGE_FILE_MACHINE_ARM64 case and a default case adding "-???" or
> something. Chances are so extremly slim that we'll ever see another
> CPU emulated on x86_64, we can always add a case for th
On Nov 26 14:27, Jeremy Drake via Cygwin-patches wrote:
> On Tue, 26 Nov 2024, Corinna Vinschen wrote:
>
> > On Nov 25 11:24, Jeremy Drake via Cygwin-patches wrote:
> > > + switch (wincap.host_machine ())
> > > + {
> > > + case IMAGE_FILE_MACHINE_AMD64:
> > > + n = stpcpy (buf, "-x64")
On Tue, 26 Nov 2024, Corinna Vinschen wrote:
> On Nov 25 11:24, Jeremy Drake via Cygwin-patches wrote:
> > + switch (wincap.host_machine ())
> > + {
> > + case IMAGE_FILE_MACHINE_AMD64:
> > + n = stpcpy (buf, "-x64") - buf;
> > + break;
> > + case IMAGE_FILE_MACHINE_ARM6
On Nov 25 11:24, Jeremy Drake via Cygwin-patches wrote:
> From: Jeremy Drake
>
> If the Cygwin dll's architecture is different from the host system's
> architecture, append an additional tag that indicates the host system
> architecture (the Cygwin dll's architecture is already indicated in
> mac
