Re: [PATCH 3/3] [RFC] Treat a gimplification failure as an internal error

2016-02-05 Thread Patrick Palka
On Thu, Jan 14, 2016 at 4:31 PM, Jeff Law wrote: > On 01/10/2016 08:20 PM, Patrick Palka wrote: >> >> On Thu, Dec 31, 2015 at 10:40 AM, Patrick Palka >> wrote: >>> >>> This patch makes it so that a gimplification failure is considered to be >>> an internal

Re: [PATCH 3/3] [RFC] Treat a gimplification failure as an internal error

2016-01-14 Thread Jeff Law
On 01/10/2016 08:20 PM, Patrick Palka wrote: On Thu, Dec 31, 2015 at 10:40 AM, Patrick Palka wrote: This patch makes it so that a gimplification failure is considered to be an internal error under normal circumstances, so that we otherwise avoid silently generating wrong

Re: [PATCH 3/3] [RFC] Treat a gimplification failure as an internal error

2016-01-10 Thread Patrick Palka
On Thu, Dec 31, 2015 at 10:40 AM, Patrick Palka wrote: > This patch makes it so that a gimplification failure is considered to be > an internal error under normal circumstances, so that we otherwise avoid > silently generating wrong code if e.g. a buggy frontend fed us a >

[PATCH 3/3] [RFC] Treat a gimplification failure as an internal error

2015-12-31 Thread Patrick Palka
This patch makes it so that a gimplification failure is considered to be an internal error under normal circumstances, so that we otherwise avoid silently generating wrong code if e.g. a buggy frontend fed us a malformed tree. The rationale for this change is that it's better to abort compilation