public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daney at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32437] [4.3 Regression] MIPS: FAIL in gcc.dg/cleanup-[8|9|10|11].c
Date: Thu, 21 Jun 2007 20:52:00 -0000	[thread overview]
Message-ID: <20070621205217.19662.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32437-7151@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from daney at gcc dot gnu dot org  2007-06-21 20:52 -------
I haven't yet looked in detail at the RTL dumps, but in the assembly output the
store of the new return value was missing.  It didn't seem to be in the wrong
place, but missing entirely.  I just hacked up the patch to see what would
happen, and it seemed to fix the problem.  I will look at the RTL dumps some
more tonight and try to determine where things went wrong.

I did however do a cross compiler test run on a remote mipsel-linux board, and
the patch fixes all 89 FAILs in the g++ testsuite.  So with the patch I am back
to zero failures in g++.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32437


  parent reply	other threads:[~2007-06-21 20:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 20:04 [Bug target/32437] New: " daney at gcc dot gnu dot org
2007-06-21  9:15 ` [Bug target/32437] " daney at gcc dot gnu dot org
2007-06-21  9:30 ` rsandifo at gcc dot gnu dot org
2007-06-21 20:52 ` daney at gcc dot gnu dot org [this message]
2007-06-22  8:38 ` daney at gcc dot gnu dot org
2007-06-22  9:12 ` rsandifo at gcc dot gnu dot org
2007-06-23  1:57 ` dave at hiauly1 dot hia dot nrc dot ca
2007-06-23  2:13 ` zadeck at naturalbridge dot com
2007-06-23 15:56 ` zadeck at naturalbridge dot com
2007-06-23 16:04 ` paolo dot bonzini at lu dot unisi dot ch
2007-06-23 16:12 ` richard dot guenther at gmail dot com
2007-06-23 16:22 ` zadeck at gcc dot gnu dot org
2007-06-23 16:23 ` zadeck at naturalbridge dot com
2007-06-23 16:47 ` daney at gcc dot gnu dot org
2007-06-23 18:41 ` dave at hiauly1 dot hia dot nrc dot ca
2007-06-26 17:14 ` daney at gcc dot gnu dot org
2007-06-26 17:27 ` zadeck at naturalbridge dot com
2007-06-26 17:46 ` dave at hiauly1 dot hia dot nrc dot ca
2007-06-26 17:54 ` zadeck at naturalbridge dot com
2007-06-27 14:37 ` richard at codesourcery dot com
2007-06-27 14:39 ` zadeck at naturalbridge dot com
2007-06-30 12:26 ` richard at codesourcery dot com
2007-06-30 17:24 ` zadeck at naturalbridge dot com
2007-06-30 17:57 ` ian at airs dot com
2007-07-01 14:45 ` zadeck at naturalbridge dot com
2007-09-29 22:42 ` daney at gcc dot gnu dot org

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=20070621205217.19662.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).