From: "H . J . Lu" <hjl@lucon.org>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org, binutils@sourceware.cygnus.com, linux-mips@oss.sgi.com
Subject: Re: DWARF2 exception doesn't work with gcc and gas on MIPS.
Date: Thu, 14 Jun 2001 12:25:50 -0700 [thread overview]
Message-ID: <20010614122550.B3668@lucon.org> (raw)
In-Reply-To: <20010614120543.B28888@redhat.com>; from rth@redhat.com on Thu, Jun 14, 2001 at 12:05:43PM -0700
On Thu, Jun 14, 2001 at 12:05:43PM -0700, Richard Henderson wrote:
> +
> + (define_insn "exception_receiver"
> + [(unspec_volatile [(const_int 0)] 4)]
> + "TARGET_ABICALLS && (mips_abi == ABI_32 || mips_abi == ABI_O64)"
> + "*
> + {
> + rtx loc;
> +
> + operands[0] = gen_rtx_REG (Pmode, PIC_FUNCTION_ADDR_REGNUM);
> +
> + if (frame_pointer_needed)
> + loc = hard_frame_pointer_rtx;
> + else
> + loc = stack_pointer_rtx;
> + loc = plus_constant (loc, current_frame_info.args_size);
> + operands[1] = gen_rtx_MEM (Pmode, loc);
> +
> + return mips_move_1word (operands, insn, 0);
> + }"
> + [(set_attr "type" "load")
> + (set_attr "length" "8")])
> \f
I have 3 questions:
1. I see PIC_FUNCTION_ADDR_REGNUM be $25. gp is $28. How does your
patch restore $28?
2. I assum you set length to 8 for o64. Has anyone checked if the
instruction is 8 byte on o64?
2. Did you remove (set_attr "mode" "SI") for o64?
Thanks.
H.J.
next prev parent reply other threads:[~2001-06-14 19:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-14 4:29 DWARF2 exception doesn't work with gcc and gas on MIPS H . J . Lu
2001-06-14 5:50 ` Ian Lance Taylor
2001-06-14 5:53 ` Ian Lance Taylor
2001-06-14 6:23 ` H . J . Lu
2001-06-14 17:19 ` Richard Henderson
2001-06-14 18:41 ` H . J . Lu
2001-06-14 19:05 ` Richard Henderson
2001-06-14 19:25 ` H . J . Lu [this message]
2001-06-14 19:42 ` Richard Henderson
2001-06-14 19:55 ` H . J . Lu
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=20010614122550.B3668@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sourceware.cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=linux-mips@oss.sgi.com \
--cc=rth@redhat.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