From: Dan Koppel <superluminal1905@yahoo.com>
To: caml-list@yquem.inria.fr
Subject: Re: Re: [Caml-list] compiler bug?
Date: Wed, 17 May 2006 23:32:21 -0700 (PDT) [thread overview]
Message-ID: <20060518063221.71418.qmail@web32208.mail.mud.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
Hi John,
Thanks for your answer. I'm running on a Power Mac. Why does the compiler store on the stack when there's a function call but not otherwise. I learned in basic compiler theory that when a function is called, you save all the registers before entering the function. So why would the compiler not simply use the register for the variable, knowing that when the time comes to call the function, the register will be saved at that point in time. That would seem a much better way to do things (thus avoiding the present problem).
- Dan
---------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.
[-- Attachment #2: Type: text/html, Size: 848 bytes --]
reply other threads:[~2006-05-18 6:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060518063221.71418.qmail@web32208.mail.mud.yahoo.com \
--to=superluminal1905@yahoo.com \
--cc=caml-list@yquem.inria.fr \
/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).