public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at tuliptree dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19357] ICE when long double argument arrives in general register
Date: Fri, 14 Jan 2005 21:52:00 -0000 [thread overview]
Message-ID: <20050114215157.11965.qmail@sourceware.org> (raw)
In-Reply-To: <20050110114611.19357.jbeulich@novell.com>
------- Additional Comments From wilson at tuliptree dot org 2005-01-14 21:51 -------
Subject: Re: ICE when long double argument arrives in
general register
On Fri, 2005-01-14 at 00:58, jbeulich at novell dot com wrote:
> ------- Additional Comments From jbeulich at novell dot com 2005-01-14 08:58 -------
> Isn't the MEM case moving things in the wrong direction? If so, and since I
> tried to fix this myself before submitting the bug, simply swapping the operands
> of emit_move_insn doesn't seem to work (made the compiler die when optimizing
> for me).
Yes. Stupid mistake on my part. I switched the operands and everything
seems OK.
What exactly was the problem you saw? I don't see a problem with my
fixed patch, with or without optimization, with my testcase. Was the
problem with your own patch? Maybe there was some other problem with
your patch. If the problem is with my patch, then I need to know how to
reproduce it in order to fix it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19357
next prev parent reply other threads:[~2005-01-14 21:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 11:46 [Bug target/19357] New: " jbeulich at novell dot com
2005-01-10 11:46 ` [Bug target/19357] " jbeulich at novell dot com
2005-01-10 15:31 ` pinskia at gcc dot gnu dot org
2005-01-14 4:03 ` wilson at gcc dot gnu dot org
2005-01-14 8:58 ` jbeulich at novell dot com
2005-01-14 21:52 ` wilson at tuliptree dot org [this message]
2005-01-17 8:06 ` jbeulich at novell dot com
2005-01-18 3:51 ` cvs-commit at gcc dot gnu dot org
2005-01-18 4:20 ` wilson at gcc dot gnu dot org
2005-04-20 2:01 ` pinskia 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=20050114215157.11965.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).