public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eljay Love-Jensen <eljay@adobe.com>
To: Vinay <vinaymr_02@yahoo.co.in>, gcc-help@gcc.gnu.org
Subject: Re: (Question reframed)Storing specified variables in the same  memory page!
Date: Wed, 13 Oct 2004 18:59:00 -0000	[thread overview]
Message-ID: <6.1.2.0.2.20041013135648.01ef8a98@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <20041013180434.88918.qmail@web8505.mail.in.yahoo.com>

Hi Vinay,

Before worrying about this memory optimization, first get the program to 
work the normal way.

Then, after the program is working, try to optimize the variable placement 
by allocating a chunk of memory.  Put the variables in that allocated 
memory chunk.

HTH,
--Eljay

  reply	other threads:[~2004-10-13 18:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11 15:53 Storing " Vinay
2004-10-11 15:57 ` Sriharsha Vedurmudi
2004-10-11 16:08   ` Vinay
2004-10-13  8:51     ` energon
2004-10-13 18:49       ` (Question reframed)Storing " Vinay
2004-10-13 18:59         ` Eljay Love-Jensen [this message]
2004-10-14  5:13         ` Sriharsha Vedurmudi
2004-10-15 13:29           ` energon

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=6.1.2.0.2.20041013135648.01ef8a98@iplan-mn.corp.adobe.com \
    --to=eljay@adobe.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=vinaymr_02@yahoo.co.in \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).