Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #70966 > unrolled thread

Re: Let's see who can be the most off-topic

Back to article view | Back to comp.lang.c

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Let's see who can be the most off-topic gordonb.u38i6@burditt.org (Gordon Burditt) - 2015-09-20 01:13 -0500
    Re: Let's see who can be the most off-topic Gareth Owen <gwowen@gmail.com> - 2015-09-20 07:19 +0100

#70966 — Re: Let's see who can be the most off-topic

>> Seems kind of odd to me that God would make eternal salvation

God is just another example of undefined behavior in comp.lang.c .
There is no mention of God in the Trinity of Holy Books:  the ISO
C standards often referred to as C90, C99, and C11.

> Can we interpret the C standard to mean what we want. Can I say that, within
> the "penumbra of meaning" of the definition of int, there's requirement that
> an int be able to index any array (thus any int that is not 64 bits on a machine
> with more the 2GB address space is non-conforming).
> Or is there some restriction? If so, what is it?

There is no guarantee that you will be able to allocate an array
of ints (or any other single object) that occupies more than 4G on
a 64-bit machine.

(a) If it's a 32-bit user process on a 64-bit machine, you don't
have the address space, which is limited to 4G or less inside
the user process.

(b) If the machine doesn't have more than 4G of RAM + backing
store - what's reserved for the OS, you can't allocate that
much.

(c) The OS may restrict the amount of memory given to any one user
process to a fraction of total available memory, for reasons such
as not having one process hog the entire machine and deadlock
prevention,

(d) The OS may limit contiguous allocations in size, especially 
if it has and uses segmented hardware, so although getting 24G
of memory may be easy, getting *contiguous* memory greater than
4G may be impossible.  (For an example of this, look at the memory
models of x86 machines where segments were limited to 64k and
all objects had to completely fit in a segment.)

[toc] | [next] | [standalone]

#70967

gordonb.u38i6@burditt.org (Gordon Burditt) writes:

>>> Seems kind of odd to me that God would make eternal salvation
>
> God is just another example of undefined behavior in comp.lang.c .

Where as in Fortran, God is real (unless explicitly declared otherwise)

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.c

csiph-web