This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Non-call exceptions and libcalls
- To: aph at cambridge dot redhat dot com, gcc at gcc dot gnu dot org
- Subject: Re: Non-call exceptions and libcalls
- From: mike stump <mrs at windriver dot com>
- Date: Tue, 19 Jun 2001 18:17:30 -0700 (PDT)
> From: Andrew Haley <aph@cambridge.redhat.com>
> Date: Tue, 19 Jun 2001 17:13:18 +0100 (BST)
> To: gcc@gcc.gnu.org
> All libcalls are marked as "cannot throw", but in the case of
> -fnon-call-exceptions this isn't true: if a divide insn can throw an
> exception, so can a call to __divdi3.
> What do people think?
I think that's a fine sledge hammer, though, I can't help but wonder
if with just a little bit more work, we could fine tune it so that
only the few routines that might throw get this type of treatment.