From: Segher Boessenkool <segher@kernel.crashing.org>
To: Andreas Schwab <schwab@suse.de>
Cc: gcc-patches@gcc.gnu.org, bergner@linux.ibm.com
Subject: Re: [PATCH] combine: Do not combine moves from hard registers
Date: Tue, 23 Oct 2018 16:28:00 -0000 [thread overview]
Message-ID: <20181023152815.GL5205@gate.crashing.org> (raw)
In-Reply-To: <mvmy3aor8vd.fsf@suse.de>
On Tue, Oct 23, 2018 at 05:16:38PM +0200, Andreas Schwab wrote:
> This miscompiles libffi and libgo on ia64.
Ouch. I cannot read ia64 machine code without a lot of handholding...
Any hints what is wrong?
Segher
next prev parent reply other threads:[~2018-10-23 15:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 21:06 Segher Boessenkool
2018-10-22 22:07 ` Jeff Law
2018-10-22 22:46 ` Segher Boessenkool
2018-10-23 10:54 ` Christophe Lyon
2018-10-23 12:36 ` Christophe Lyon
2018-10-23 13:10 ` Segher Boessenkool
2018-10-23 13:30 ` Christophe Lyon
2018-10-23 13:08 ` Segher Boessenkool
2018-10-23 13:50 ` Christophe Lyon
2018-10-24 1:50 ` Segher Boessenkool
2018-10-24 9:52 ` Christophe Lyon
2018-11-02 22:19 ` Renlin Li
2018-11-02 23:03 ` Segher Boessenkool
2018-11-02 23:54 ` Segher Boessenkool
2018-11-03 2:34 ` Jeff Law
2018-11-05 12:35 ` Renlin Li
2018-11-05 18:16 ` Renlin Li
2018-11-07 23:02 ` Segher Boessenkool
2018-11-09 10:21 ` Richard Earnshaw (lists)
2018-11-05 22:50 ` Segher Boessenkool
2018-10-24 9:38 ` Paul Hua
2018-10-23 16:16 ` Andreas Schwab
2018-10-23 16:28 ` Segher Boessenkool [this message]
2018-10-24 12:24 ` Andreas Schwab
2018-10-26 17:41 ` Steve Ellcey
2018-10-26 18:37 ` Segher Boessenkool
[not found] ` <7bc8697f-a09e-627f-b032-eba5ecb682ac@arm.com>
2018-11-08 20:34 ` Segher Boessenkool
2018-11-09 21:12 ` Jeff Law
2018-11-10 4:51 ` Segher Boessenkool
2018-11-10 16:54 ` Jeff Law
2018-11-12 11:57 ` Sam Tebbs
[not found] ` <e9104024-2f6a-6cb8-e366-39b96f7a72f2@arm.com>
2018-11-12 12:54 ` Segher Boessenkool
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=20181023152815.GL5205@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@suse.de \
/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).