> On Aug 3, 2021, at 2:39 PM, Iain Sandoe wrote:
>
>
>
>> On 2 Aug 2021, at 22:37, Matt Jacobson via Gcc-patches
>> wrote:
>>
>>> On Aug 2, 2021, at 5:09 PM, Eric Gallager wrote:
>>>
>>> On Wed, Jul 28, 2021 at 11:36 PM Matt Jacobson via Gcc-patches
>>> wrote:
As is, an
> On 2 Aug 2021, at 22:37, Matt Jacobson via Gcc-patches
> wrote:
>
>> On Aug 2, 2021, at 5:09 PM, Eric Gallager wrote:
>>
>> On Wed, Jul 28, 2021 at 11:36 PM Matt Jacobson via Gcc-patches
>> wrote:
>>>
>>> As is, an invocation of GCC with -fnext-runtime -fobjc-abi-version=2
>>>
> On Aug 2, 2021, at 5:09 PM, Eric Gallager wrote:
>
> On Wed, Jul 28, 2021 at 11:36 PM Matt Jacobson via Gcc-patches
> wrote:
>>
>> As is, an invocation of GCC with -fnext-runtime -fobjc-abi-version=2 crashes,
>> unless target-specific code adds an implicit -fno-objc-sjlj-exceptions (which
On Wed, Jul 28, 2021 at 11:36 PM Matt Jacobson via Gcc-patches
wrote:
>
> As is, an invocation of GCC with -fnext-runtime -fobjc-abi-version=2 crashes,
> unless target-specific code adds an implicit -fno-objc-sjlj-exceptions (which
> Darwin does).
>
> This patch makes the general case not crash.
As is, an invocation of GCC with -fnext-runtime -fobjc-abi-version=2 crashes,
unless target-specific code adds an implicit -fno-objc-sjlj-exceptions (which
Darwin does).
This patch makes the general case not crash.
I don't have commit access, so if this patch is suitable, I'd need someone else