From: Andrew Cagney <ac131313@cygnus.com>
To: David B Anderson <davea@quasar.engr.sgi.com>
Cc: gdb-patches@sources.redhat.com, drow@mvista.com
Subject: Re: [rfa] mips argument passing fixes for o32
Date: Wed, 18 Jul 2001 13:29:00 -0000 [thread overview]
Message-ID: <3B55F1A2.9080108@cygnus.com> (raw)
In-Reply-To: <200107171447.HAA66261@quasar.engr.sgi.com>
>>GCC is always left shifting s1 in a register (regardless of -EL or EB).
>
>
>
> Well....
> proton 25% cc -c -32 t3.c -show
> /usr/lib/cc -DEFAULT:abi=n32:isa=mips4:proc=r10k -c -32 t3.c -show
> /usr/lib/cfe -D_MIPS_FPSET=16 -D_MIPS_ISA=2 -D_ABIO32=1 -D_MIPS_SIM=_ABIO32 -D_MIPS_SZINT=32 -D_MIPS_SZLONG=32 -D_MIPS_SZPTR=32 -D_SIZE_INT=32 -D_SIZE_LONG=32 -D_SIZE_PTR=32 -D__EXTENSIONS__ -DLANGUAGE_C -D_LANGUAGE_C -D__INLINE_INTRINSICS -Dsgi -D__sgi -Dunix -Dmips -Dhost_mips -D__unix -D__host_mips -D_SVR4_SOURCE -D_MODERN_C -D_SGI_SOURCE -D_PIC -D__DSO__ -DSYSTYPE_SVR4 -D_SYSTYPE_SVR4 -D_LONGLONG -D__mips=2 -I -D_MIPSEB -DMIPSEB -D__STDC__=1 -I/usr/include t3.c -Xv -D_CFE -Amachine(mips) -Asystem(unix) -call_shared -G 0 -std -XS/tmp/ctmsta000Ss -mips2 -EB -Xg0 -O1 > /tmp/ctmfa000Ss
> cfe: main /usr/lib/ugen -v -G 0 -pic2 -mips2 -EB -g0 -O1 /tmp/ctmfa000Ss -o /tmp/ctmca000Ss -t /tmp/ctmsta000Ss -temp /tmp/ctmgta000Ss
> ugen: main
> /usr/lib/as1 -t5_ll_sc_bug -elf -pic2 -v -G 0 -p0 -mips2 -EB -g0 -O1 /tmp/ctmca000Ss -o t3.o -t /tmp/ctmsta000Ss
> as1: main
> proton 26% dis t3.o
> [ 7] 0x 0: 3c 1c 00 00 lui gp,0
> [ 7] 0x 4: 27 9c 00 00 addiu gp,gp,0
> [ 7] 0x 8: 03 99 e0 21 addu gp,gp,t9
> [ 8] 0x c: 8f 8e 00 00 lw t2,0(gp)
> [ 8] 0x 10: 8f 99 00 00 lw t9,0(gp)
> [ 7] 0x 14: 27 bd ff e0 addiu sp,sp,-32
> [ 8] 0x 18: 91 ce 00 00 lbu t2,0(t2)
> [ 7] 0x 1c: af bf 00 1c sw ra,28(sp)
> [ 7] 0x 20: af bc 00 18 sw gp,24(sp)
> [ 8] 0x 24: a3 ae 00 00 sb t2,0(sp)
> [ 8] 0x 28: 03 20 f8 09 jalr t9
> [ 8] 0x 2c: 8f a4 00 00 lw a0,0(sp)
>
> And -EL seems to generate the same instructions (but I don't quite
> trust -EL).
Now I'm really confused, that is -EB -o32 and no shift. I think I'll try to scrounge up an IRIX box and have a play.
Andrew
next prev parent reply other threads:[~2001-07-18 13:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 17:03 David B Anderson
2001-07-15 14:50 ` Andrew Cagney
2001-07-15 15:22 ` Daniel Jacobowitz
2001-07-16 7:46 ` Andrew Cagney
2001-07-15 20:29 ` David B Anderson
2001-07-16 16:44 ` Andrew Cagney
2001-07-17 7:49 ` David B Anderson
2001-07-18 13:29 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-06 11:26 Daniel Jacobowitz
2001-07-06 14:24 ` Andrew Cagney
2001-07-12 0:47 ` Andrew Cagney
2001-07-12 10:35 ` Daniel Jacobowitz
2001-07-12 1:23 ` Andrew Cagney
2001-07-12 10:39 ` Daniel Jacobowitz
2001-07-12 11:59 ` Andrew Cagney
2001-07-12 12:21 ` Daniel Jacobowitz
2001-07-12 12:38 ` Andrew Cagney
[not found] ` <3B58AEBE.1000304@cygnus.com>
[not found] ` <20010720152547.A10028@nevyn.them.org>
2001-07-20 16:35 ` Andrew Cagney
2001-07-20 16:46 ` Elena Zannoni
2001-07-23 20:36 ` Andrew Cagney
2001-11-14 14:15 ` Daniel Jacobowitz
2001-11-27 7:48 ` Daniel Jacobowitz
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=3B55F1A2.9080108@cygnus.com \
--to=ac131313@cygnus.com \
--cc=davea@quasar.engr.sgi.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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