From: "William N. Zanatta" <william@veritel.com.br>
To: Glynn Clements <glynn.clements@virgin.net>
Cc: "'linux-c-programming@vger.kernel.org'"
<linux-c-programming@vger.kernel.org>
Subject: Re: GCC and Memory Organization
Date: Thu, 11 Apr 2002 10:22:48 -0300 [thread overview]
Message-ID: <3CB58E28.1030201@veritel.com.br> (raw)
In-Reply-To: 15539.26431.760192.203498@cerise.nosuchdomain.co.uk
>
> This isn't a compiler issue. The different layouts would require
> different source code. The former corresponds to a one-dimensional
> array, while the latter corresponds to a two-dimensional array.
>
I guess I found something. Looks like I'm talking about the concepts of
segmentation and paging. Is that right?
In the following site there's a interesting map for understanding the
concepts of VM.
http://cne.gmu.edu/modules/vm/index.html
Thank you again,
William
next prev parent reply other threads:[~2002-04-11 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 15:07 GCC and Memory Organization William N. Zanatta
2002-04-09 22:12 ` Glynn Clements
2002-04-11 12:48 ` William N. Zanatta
2002-04-11 13:22 ` William N. Zanatta [this message]
2002-04-11 14:07 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CB58E28.1030201@veritel.com.br \
--to=william@veritel.com.br \
--cc=glynn.clements@virgin.net \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).