This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: -fomit-frame-pointer and exceptions or setjmp/longjmp
- From: Denis Zaitsev <zzz at cd-club dot ru>
- To: Richard Henderson <rth at redhat dot com>, Nix <nix at esperi dot demon dot co dot uk>,gcc at gcc dot gnu dot org
- Date: Wed, 3 Jul 2002 14:32:03 +0600
- Subject: Re: PATCH: -fomit-frame-pointer and exceptions or setjmp/longjmp
- References: <20020603032930.A23158@natasha.zzz.zzz> <20020602151141.A13006@redhat.com> <87fzzuc12b.fsf@amaterasu.srvr.nix> <20020614052419.A6289@natasha.zzz.zzz> <87it4l8z43.fsf@amaterasu.srvr.nix> <20020702050849.A13730@natasha.zzz.zzz> <20020702164555.A2299@redhat.com>
On Tue, Jul 02, 2002 at 04:45:55PM -0700, Richard Henderson wrote:
> On Tue, Jul 02, 2002 at 05:08:49AM +0600, Denis Zaitsev wrote:
> While this patch may or may not be correct, it is definitely
> the only problem. See PR 6678 for an example that does not
> require -fpic at all.
The call frame info has other problems too, if you are talking about
that. But these are the other, not this problem. BTW, where PR 6678
is? I haven't found it in the list.
> In any case, I won't apply this. I'd rather see the POP insn
> merged into the prologue_get_pc pattern.
Will it be merged or won't, how will it influence over the
relationship between the call insn and dwarf2out_frame_debug_expr's
behaviour? I mean that this is a very special call, and so it should
be followed with the instructions for the call frame info generation,
else dwarf2out_frame_debug_expr does the wrong things. What do you
think is wrong here?