From: Nathan Sidwell <nathan@acm.org>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: Andreas Schwab <schwab@suse.de>, Jason Merrill <jason@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [C++/58583] ICE instantiating NSDMIs
Date: Wed, 17 Jun 2015 15:41:00 -0000 [thread overview]
Message-ID: <5581941E.70601@acm.org> (raw)
In-Reply-To: <20150617085738.GA22950@arm.com>
On 06/17/15 04:57, James Greenhalgh wrote:
> I'm seeing the same issues on aarch64-none-elf and aarch64_be-none-elf
> in one of my testing environments, but, interestingly, not on
> aarch64-none-linux-gnu or in my other aarch64-none-elf testing
> environment (!!).
ugh. What is the behavior on the testcase with the patch reverted? Is it the
same on both elf systems? (I'm expecting an ICE in one of the tsubst variants
when it meets a DEFAULT_ARG)
> I've pasted both log extracts below (after
> stripping the file paths for each build environment, so you can see just
> how similar the invocations are!). The PASSing environment does use a
> slightly more modern toolchain for building the cross-toolchain (PASSing
> environment uses 4.9.2, FAILing environment uses 4.8.1), so that could
> be a source of the difference?
ew.
nathan
next prev parent reply other threads:[~2015-06-17 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 1:07 Nathan Sidwell
2015-06-08 17:47 ` Jason Merrill
2015-06-08 20:25 ` Nathan Sidwell
2015-06-09 13:49 ` Nathan Sidwell
2015-06-15 2:34 ` Nathan Sidwell
2015-06-15 16:18 ` Jason Merrill
2015-06-16 8:20 ` Andreas Schwab
2015-06-16 17:15 ` Nathan Sidwell
2015-06-17 9:14 ` James Greenhalgh
2015-06-17 15:41 ` Nathan Sidwell [this message]
2015-06-20 7:12 ` Andreas Schwab
2015-06-21 23:05 ` Nathan Sidwell
2015-06-22 1:47 ` Nathan Sidwell
2015-06-22 7:57 ` Andreas Schwab
2015-06-22 16:15 ` Nathan Sidwell
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=5581941E.70601@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=jason@redhat.com \
--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).