From: Savithri Muthukumar <savi@c-cube.com>
To: "'bug-gcc@prep.ai.mit.edu'" <bug-gcc@gnu.org>
Cc: "'help-gcc@prep.ai.mit.edu'" <help-gcc@gnu.org>
Subject: Rebuilding GNU CC
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <01BF4199.DF952B00.savi@c-cube.com> (raw)
Message-ID: <19991231222400.elFF0QQjuBIqO-MXnkEPrTtImEovGYsM97yxtjvAcns@z> (raw)
Hi,
I am working on rebulding the GNU CC so that
there is no need for extra memory space to store
the arguments ,return address,local variables of a fnction
assuming that there won't be an overloop in the eight
registers(SPARC machine) to store more than eight function calls.
I need help regarding which macro or flah has to be set in
which file inorder to have this feature in GNU CC for SPARC-out
target machine.
next reply other threads:[~1999-12-31 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-08 16:31 Savithri Muthukumar [this message]
1999-12-31 22:24 ` Savithri Muthukumar
1999-12-08 18:41 Mike Stump
1999-12-31 22:24 ` Mike Stump
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=01BF4199.DF952B00.savi@c-cube.com \
--to=savi@c-cube.com \
--cc=bug-gcc@gnu.org \
--cc=help-gcc@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).