public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@cygnus.com>
To: Mike Stump <mrs@wrs.com>
Cc: kenner@vlsi1.ultra.nyu.edu, egcs@cygnus.com
Subject: Re: improved i960 builtin setjmp/longjmp handling
Date: Thu, 23 Apr 1998 23:53:00 -0000	[thread overview]
Message-ID: <19980423235331.31279@dot.cygnus.com> (raw)
In-Reply-To: <199804232233.PAA24114@kankakee.wrs.com>

> ! #if defined (HAVE_nonlocal_goto) && defined (NEED_HARD_FRAME_FOR_NONLOCAL_GOTO)
> !   if (HAVE_nonlocal_goto && NEED_HARD_FRAME_FOR_NONLOCAL_GOTO)
> !     /* We store the frame pointer and the address of lab1 in the buffer
> !        and use the rest of it for the stack save area, which is
> !        machine-dependent.  */
> !     emit_move_insn (gen_rtx_MEM (Pmode, buf_addr),
> ! 		    hard_frame_pointer_rtx);
> !   else
> ! #endif
> !     /* We store the frame pointer and the address of lab1 in the buffer
> !        and use the rest of it for the stack save area, which is
> !        machine-dependent.  */
> !     emit_move_insn (gen_rtx_MEM (Pmode, buf_addr),
> ! 		    virtual_stack_vars_rtx);
> ! 

I would suggest one of two alternate courses:

  (1) Define builtin_setjmp_setup to store the hard frame pointer, either
      on top of the v_s_v_rtx, or in unused slots 4 or 5.

  (2) Define a macro that is an expression that evaluates to an rtx to
      use, and default that macro to v_s_v_rtx.  The i960 header can then
      define it to h_f_p_rtx directly.


r~

      reply	other threads:[~1998-04-23 23:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-23 18:49 Mike Stump
1998-04-23 23:53 ` Richard Henderson [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=19980423235331.31279@dot.cygnus.com \
    --to=rth@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --cc=mrs@wrs.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).