From: Jim Wilson <wilson@cygnus.com>
To: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: egcs@cygnus.com
Subject: Re: Results for haifa-disabled egcs-980214 testsuite on mips-sgi-irix6.3
Date: Mon, 16 Feb 1998 18:54:00 -0000 [thread overview]
Message-ID: <199802170254.SAA11888@rtl.cygnus.com> (raw)
In-Reply-To: <199802161814.QAA10848@tiete.dcc.unicamp.br>
FAIL: g++.eh/cleanup1.C Execution test
FAIL: g++.eh/flow1.C Execution test
FAIL: g++.eh/new1.C Execution test
...
I just checked in a fix for this yesterday. I got only one unexpected failure
(g++.brendan/groff1.C) when I ran the testsuite with my patch.
Sun Feb 15 17:04:13 1998 Jim Wilson <wilson@cygnus.com>
* mips/mips.h (INITIAL_ELIMINATION_OFFSET): Readd Jun 6 change.
Index: mips.h
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/gcc/config/mips/mips.h,v
retrieving revision 1.15
diff -p -r1.15 mips.h
*** mips.h 1998/02/11 13:04:01 1.15
--- mips.h 1998/02/16 01:03:52
*************** extern struct mips_frame_info current_fr
*** 2152,2159 ****
- ((mips_abi != ABI_32 && mips_abi != ABI_EABI) \
? current_function_pretend_args_size \
: 0)); \
else if ((FROM) == RETURN_ADDRESS_POINTER_REGNUM) \
! (OFFSET) = current_frame_info.gp_sp_offset; \
}
/* If we generate an insn to push BYTES bytes,
--- 2152,2163 ----
- ((mips_abi != ABI_32 && mips_abi != ABI_EABI) \
? current_function_pretend_args_size \
: 0)); \
+ /* Some ABIs store 64 bits to the stack, but Pmode is 32 bits, \
+ so we must add 4 bytes to the offset to get the right value. */ \
else if ((FROM) == RETURN_ADDRESS_POINTER_REGNUM) \
! (OFFSET) = current_frame_info.gp_sp_offset \
! + ((UNITS_PER_WORD - (POINTER_SIZE / BITS_PER_UNIT)) \
! * (BYTES_BIG_ENDIAN != 0)); \
}
/* If we generate an insn to push BYTES bytes,
next prev parent reply other threads:[~1998-02-16 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-16 16:56 Alexandre Oliva
1998-02-16 18:54 ` Jim Wilson [this message]
1998-02-16 17:38 Alexandre Oliva
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=199802170254.SAA11888@rtl.cygnus.com \
--to=wilson@cygnus.com \
--cc=egcs@cygnus.com \
--cc=oliva@dcc.unicamp.br \
/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).