On 10/12/2011 09:54 AM, Kai Tietz wrote:
> +;; We need to disable this for TARGET_SEH, as otherwise
> +;; shrink-wrapped prologue gets enabled too. This might exceed
> +;; the maximum size of prologue in unwind information.
> +
> (define_expand "simple_return"
>[(simple_return)]
> - ""
> +
2011/10/12 Richard Henderson :
> On 10/12/2011 12:07 AM, Kai Tietz wrote:
>> Hello,
>>
>> by recent changes gcc begun to move code into the prologue region.
>> This is for x64 SEH an issue, as here the table-information for
>> prologue is limited to 255 bytes size. So we need to avoid moving
>> ad
On 10/12/2011 12:07 AM, Kai Tietz wrote:
> Hello,
>
> by recent changes gcc begun to move code into the prologue region.
> This is for x64 SEH an issue, as here the table-information for
> prologue is limited to 255 bytes size. So we need to avoid moving
> additional code into prologue. To achie
Hello,
by recent changes gcc begun to move code into the prologue region.
This is for x64 SEH an issue, as here the table-information for
prologue is limited to 255 bytes size. So we need to avoid moving
additional code into prologue. To achieve this we mark all standard
and xmm registers as pro
