public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38130] [4.4 regression]__builtin_alloca (vs IRA?)  testsuite failures on  mingw32
Date: Tue, 18 Nov 2008 05:57:00 -0000	[thread overview]
Message-ID: <20081118055546.15447.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38130-4066@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from dannysmith at users dot sourceforge dot net  2008-11-18 05:55 -------
(In reply to comment #4)
> Created an attachment (id=16713)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16713&action=view) [edit]
> gcc44-pr38130.patch
> 
> I've talked about this with Honza on IRC:
> <honza> I would just use "0" constraint. At least in old times with regmove,
> regmove was able to discover that it should use same pseudo for input and
> output.  If you use pair of "=a" and "a" only reload sees this fact
> <honza> so patch is OK with that change.
> This is an updated patch which uses "0" instead of "a" constraint for operand
> 1.
> So, can anyone please test it?  Thanks.
> 

This patch  bootstraps on mingw32 (c,c++,gfortran) successfully,  libstcd++ now
compiles and the two testcases reported as failing now pass.

A full regtest is in progress and so far looks good.

Thanks


-- 


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


  parent reply	other threads:[~2008-11-18  5:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15  9:27 [Bug target/38130] New: [4.4.0 " dannysmith at users dot sourceforge dot net
2008-11-16  2:52 ` [Bug target/38130] [4.4 " pinskia at gcc dot gnu dot org
2008-11-16  9:05 ` ktietz at gcc dot gnu dot org
2008-11-17  9:22 ` jakub at gcc dot gnu dot org
2008-11-17  9:36 ` jakub at gcc dot gnu dot org
2008-11-17 22:13 ` jakub at gcc dot gnu dot org
2008-11-17 22:30 ` jakub at gcc dot gnu dot org
2008-11-18  5:57 ` dannysmith at users dot sourceforge dot net [this message]
2008-11-18 12:36 ` jakub at gcc dot gnu dot org
2008-11-18 12:39 ` jakub 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=20081118055546.15447.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).