This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Functions that always return
- To: rth at cygnus dot com
- Subject: Re: Functions that always return
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Sun, 29 Oct 00 12:27:03 EST
- Cc: gcc at gcc dot gnu dot org
Well, so long as you don't mind if stuff that can potentially
trap being moved across these functions. If you do care, you
can't mark anything constant.
Note the scenario here: an Ada procedure X calls a C++ function A,
which calls a constant function B (also in C++) and B gets a stack
overflow. That will cause a Storage_Error exception which, if caught
at all, will be in X or above.
Can you explain what you mean in conjuction with this scenario?