On Monday, 11 August 2014 at 06:17:22 UTC, ketmar via
Digitalmars-d-learn wrote:
On Mon, 11 Aug 2014 05:18:59 +
Jeremy DeHaan via Digitalmars-d-learn
digitalmars-d-learn@puremagic.com wrote:
why do you need that info? D types has well-defined sizes (i.e
uint is
always 32 bits, and so on).
On Mon, 11 Aug 2014 05:18:59 +
Jeremy DeHaan via Digitalmars-d-learn
digitalmars-d-learn@puremagic.com wrote:
why do you need that info? D types has well-defined sizes (i.e uint is
always 32 bits, and so on).
you still can check pointer size -- (void *).sizeof. but i'm pretty
sure that you
On 11/08/14 07:18, Jeremy DeHaan wrote:
I am looking at these versions as described here:
http://dlang.org/version.html
There are X86 and X86_64 version identifiers, but these specifically
mention that they are versions for the processor type. Can they also be
used to determine if the OS is
On Monday, 11 August 2014 at 05:19:01 UTC, Jeremy DeHaan wrote:
I am looking at these versions as described here:
http://dlang.org/version.html
There are X86 and X86_64 version identifiers, but these
specifically mention that they are versions for the processor
type. Can they also be used to
On Monday, 11 August 2014 at 07:58:15 UTC, Freddy wrote:
If you want to check if
the target OS(not your code) is running 32 vs 64 bit you have
to do system call for your target OS.
Not the OS, but a special CPU instruction: isX86_64() in
core.cpuid?
On Mon, 11 Aug 2014 12:51:40 +
via Digitalmars-d-learn digitalmars-d-learn@puremagic.com wrote:
Not the OS, but a special CPU instruction: isX86_64() in
core.cpuid?
but there is ARM64 coming. and gdc, for example, will has no problems
to support it out of the box due to using gcc cogegen.
I am looking at these versions as described here:
http://dlang.org/version.html
There are X86 and X86_64 version identifiers, but these
specifically mention that they are versions for the processor
type. Can they also be used to determine if the OS is running in
32 vs 64 bits?
