From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Markus Mottl <markus@mail4.ai.univie.ac.at>
Cc: OCAML <caml-list@inria.fr>
Subject: Re: [Caml-list] byte-code and -fno-defer-pop
Date: Tue, 18 Sep 2001 16:27:30 +0200 [thread overview]
Message-ID: <20010918162730.J23689@pauillac.inria.fr> (raw)
In-Reply-To: <20010917155545.A23056@chopin.ai.univie.ac.at>; from markus@mail4.ai.univie.ac.at on Mon, Sep 17, 2001 at 03:55:45PM +0200
> C-files in the OCaml-distribution are usually compiled with -fno-defer-pop
> when they are supposed to be used with byte code, too. What is the
> rationale behind?
There used to be a bug in gcc whereas code using computed gotos (such
as the OCaml bytecode interpreter) would be incorrectly compiled
unless the -fno-defer-pop option is given. I don't know if this has
been fixed in recent versions of gcc.
At any rate, you're correct that -fno-defer-pop is needed only for
compiling byterun/interp.c, and applying it to all bytecode-related C
files is a bit excessive.
> Is this only intended to limit stack growth a bit or
> are there other reasons? This opposite of this option is normally turned
> on when optimisation (-O) is used. Would you recommend this setting
> generally for C-code that should cooperate with OCaml-byte code?
No, it shouldn't be necessary.
- Xavier Leroy
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
prev parent reply other threads:[~2001-09-18 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 13:55 Markus Mottl
2001-09-18 14:27 ` Xavier Leroy [this message]
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=20010918162730.J23689@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=markus@mail4.ai.univie.ac.at \
/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).