Quantcast

RFC: updating CPU identification macros

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RFC: updating CPU identification macros

Keith Marshall-3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Guys,

As I've noted at https://sourceforge.net/p/mingw/bugs/2301/, in both
<windows.h> and <winnt.h> I see:

  #if defined(__i686__) && !defined(_M_IX86)
  #define _M_IX86 600
  #elif defined(__i586__) && !defined(_M_IX86)
  #define _M_IX86 500
  #elif defined(__i486__) && !defined(_M_IX86)
  #define _M_IX86 400
  #elif defined(__i386__) && !defined(_M_IX86)
  #define _M_IX86 300
  #endif

This may have been okay when Anders Norlander first wrote it,
(although why he chose to duplicate it -- unnecessarily, as it happens
- -- in the two headers noted above is something of a puzzle), but I
doubt that it is good enough today.

I've indicated how I propose to update this, on the 2301 ticket, but
I'd particularly appreciate your thoughts on which, if any, of the
other Microsoft predefined macros, as documented at:
https://msdn.microsoft.com/en-us/library/b0084kay(v=vs.140).aspx
we should consider adding.  Also, how much of:

  #if defined(_M_IX86) && !defined(_X86_)
  #define _X86_
  #elif defined(_M_ALPHA) && !defined(_ALPHA_)
  #define _ALPHA_
  #elif defined(_M_PPC) && !defined(_PPC_)
  #define _PPC_
  #elif defined(_M_MRX000) && !defined(_MIPS_)
  #define _MIPS_
  #elif defined(_M_M68K) && !defined(_68K_)
  #define _68K_
  #endif

remains relevant today?  (Indeed, did Microsoft /ever/ support the
Motorola M68K processor?)

Please add your comments on the 2301 ticket.

- --
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJXTcPFAAoJEMCtNsY0flo/OEIP/2lDYl1YIzfE5/MxVXrIoj9l
npT5dUYE7ht40oPAzwkAOrB0Z7YFpsbgpVMiA1eEMtySaDz/v1ODrzrGp7t8R4YA
EGK87dKt34gT2TGudhyt5ER3xTvqynMFneIyApcLcP/Ul+0wmenP0FoMEpvGZt19
9kgl29zGBaIwFccPII8CFPARRrGycxr607nWBdpDIz/8zCsrU5tGLk3nnMZa6WB9
jOu8uzNQcKGWnpYdet/DWiRqLETxyCwAiY5mnLrWiIZw6qPDKd9U2vKjB4OB9BhU
FNzaCpU4Q70Rugzthh386M1VPUgD+5TZD4rrQ2cuUaLrgL/zgr5oKNzKX5d8dIfj
TmJuvuNnpWFzK1p5cQn5w6oZRhFzM0b+zOPXT81vVEcdQ8ysNHrGjLLV70UTziEw
Kk5yJndHqBPbLqCZC3whT24rHTlbp2/wKK8ZxRi7ZE9r+1gu86Y8SG+eWkTwn+5Y
QAnkSAMXpqGZwXR5afGjrYnxc/Clw3e3EZ8KhCvS6ovUj7hwlr5PetFD1ckumNAT
WuHOFO82zCruiXA5Ko6eHOaHhnXn8tFEWXuDwWWbqZoDNA2rMMCivdJ8kq+Gmld/
aVe/v/9vuduc/N6x23bnCG5LfZTIf6lY/tzAyv3eQE7FVwMLqzi/nz8kYhQUv86j
mNhuv1KX6ZqLZKFk4NyO
=NRJa
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
MinGW-dvlpr mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: RFC: updating CPU identification macros

Keith Marshall-3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31/05/16 18:03, Keith Marshall wrote:
> As I've noted at https://sourceforge.net/p/mingw/bugs/2301/, ...
>
> Please add your comments on the 2301 ticket.

Ping.

In the absence of any evident interest, I committed:
https://sourceforge.net/p/mingw/mingw-org-wsl/ci/39e2fc7fccb558df06e4051d147a582b115d92d3/

This adjusts the set of mapped MSVC defines to _M_IX86 and _M_IX86_FP,
or _M_X64 and _M_AMD64, or _M_IA64, as appropriate, while preserving
only the reverse mapping to _X86_, (i.e. it no longer defines _ALPHA_,
_PPC_, _MIPS_, or _68K_).

If you disagree with any of these changes, you need to respond on the
ticket, and justify your objections.

- --
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJXXE+nAAoJEMCtNsY0flo/y1QP+wWuZb8fEYJPxme70rWz0JXL
91VJ23uOLXRmg2EEh78pyXLf3RwX+l+y0o9HBiF5eDCKF38e/Eonj50uZDGJIbR5
JaORg61JjtyR7moVBkDu5uNfZ4hX0oYrE46S6BEm7b8j1C4g5YkIbJc/jhZL+EEG
e/orqBeWp6hSXHK+v/YjyQ4GpHv+tAN0dWHp+0UvCfuDefcYGoc+UNZsGxLj3TU7
d7Vh7UFB6Sy2Du1P27YhqjH/1YmBsbi8zUaIkcIPa5lyX2X2a4CO6qWH+hU6nwE5
pP/BnU8PUV7W4cHore2Ru45rVgdhEYUIObpO8Z8Ivb0fpvzKSSAhhyjLbGfor9zA
EIE3PTy2GagmscZGU4RUHTEIbEV02Q1CcI4WcGcQU/j2vzZJft6p3bE+p0RDQhkY
5noCstcAq02+/3nhHtP1Nsja1geDWAqTlh1HRb1a/lq4oKQBZ41D7idIf/OroPan
O+x4utbcUySudFIa8NsP2K4ODH4O4NCWz3U47ydzcuM2MZzHgXC2FsoWdWP9iyMU
qQXLER7xHGupJIz72549xWaZdGeUn++Cccgfdq0FSzcIEXmcQntkRUKs0KsYZt8C
lRQfVGJO7gOFDSbn0ycGBPkLDlfuABal3ExprU1FT4NLevQ194GMRpOoLvyW9pIj
H/198HL0pnyhfycbCu0d
=r9I1
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
MinGW-dvlpr mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: RFC: updating CPU identification macros

Earnie Boyd
On 6/11/2016 1:51 PM, Keith Marshall wrote:

> On 31/05/16 18:03, Keith Marshall wrote:
>> As I've noted at https://sourceforge.net/p/mingw/bugs/2301/, ...
>
>> Please add your comments on the 2301 ticket.
>
> Ping.
>
> In the absence of any evident interest, I committed:
> https://sourceforge.net/p/mingw/mingw-org-wsl/ci/39e2fc7fccb558df06e4051d147a582b115d92d3/
>
> This adjusts the set of mapped MSVC defines to _M_IX86 and _M_IX86_FP,
> or _M_X64 and _M_AMD64, or _M_IA64, as appropriate, while preserving
> only the reverse mapping to _X86_, (i.e. it no longer defines _ALPHA_,
> _PPC_, _MIPS_, or _68K_).
>
> If you disagree with any of these changes, you need to respond on the
> ticket, and justify your objections.

I think it's good.

--
Earnie

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
_______________________________________________
MinGW-dvlpr mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr
Loading...