On Tue, Aug 21, 2018 at 11:45 AM Iain Sandoe wrote:
>
>
> > On 20 Aug 2018, at 08:27, Richard Biener wrote:
> >
> > On Tue, Aug 14, 2018 at 10:18 PM Mike Stump wrote:
> >>
> >> On Aug 14, 2018, at 4:20 AM, Iain Sandoe wrote:
> >>> When function sub-sections are enabled, Darwin’s assembler needs
> On 20 Aug 2018, at 08:27, Richard Biener wrote:
>
> On Tue, Aug 14, 2018 at 10:18 PM Mike Stump wrote:
>>
>> On Aug 14, 2018, at 4:20 AM, Iain Sandoe wrote:
>>> When function sub-sections are enabled, Darwin’s assembler needs the FDE
>>> local start
>>> label for each sub-section to follo
On Tue, Aug 14, 2018 at 10:18 PM Mike Stump wrote:
>
> On Aug 14, 2018, at 4:20 AM, Iain Sandoe wrote:
> > When function sub-sections are enabled, Darwin’s assembler needs the FDE
> > local start
> > label for each sub-section to follow a linker-visible one so that the FDE
> > will be correctly
On Aug 14, 2018, at 4:20 AM, Iain Sandoe wrote:
> When function sub-sections are enabled, Darwin’s assembler needs the FDE
> local start
> label for each sub-section to follow a linker-visible one so that the FDE
> will be correctly
> associated with the code of the subsection.
>
> The current
Hi,
A more detailed explanation is in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81033#c37
When function sub-sections are enabled, Darwin’s assembler needs the FDE local
start
label for each sub-section to follow a linker-visible one so that the FDE will
be correctly
associated with the code