On Mon, Aug 28, 2017 at 10:16 AM, Richard Sandiford
wrote:
> Richard Biener writes:
>> On Thu, Aug 17, 2017 at 1:06 PM, Richard Sandiford
>> wrote
>>> Richard Biener writes:
On Thu, Aug 17, 2017 at 11:49 AM, Richard Sandiford
wrote:
> Internal functions that map directly to an op
Richard Biener writes:
> On Thu, Aug 17, 2017 at 1:06 PM, Richard Sandiford
> wrote
>> Richard Biener writes:
>>> On Thu, Aug 17, 2017 at 11:49 AM, Richard Sandiford
>>> wrote:
Internal functions that map directly to an optab can only throw an
exception for -fnon-call-exceptions. Thi
On Thu, Aug 17, 2017 at 1:06 PM, Richard Sandiford
wrote
> Richard Biener writes:
>> On Thu, Aug 17, 2017 at 11:49 AM, Richard Sandiford
>> wrote:
>>> Internal functions that map directly to an optab can only throw an
>>> exception for -fnon-call-exceptions. This patch handles that in
>>> inter
Richard Biener writes:
> On Thu, Aug 17, 2017 at 11:49 AM, Richard Sandiford
> wrote:
>> Internal functions that map directly to an optab can only throw an
>> exception for -fnon-call-exceptions. This patch handles that in
>> internal_fn_flags, in a similar way to ATTR_*NOTHROW in builtins.def.
On Thu, Aug 17, 2017 at 11:49 AM, Richard Sandiford
wrote:
> Internal functions that map directly to an optab can only throw an
> exception for -fnon-call-exceptions. This patch handles that in
> internal_fn_flags, in a similar way to ATTR_*NOTHROW in builtins.def.
>
> (Functions that don't throw
