On Tue, Aug 29, 2017 at 5:47 PM, DJ Delorie wrote:
>
> Richard Biener writes:
>> Humm... don't you have to register interrupt handlers somehow?
>
> MSP430 uses an "if they're present, they're registered" approach, so
> it's driven by the user tagging functions as interrupts - the linker
> notices
Richard Biener writes:
> Humm... don't you have to register interrupt handlers somehow?
MSP430 uses an "if they're present, they're registered" approach, so
it's driven by the user tagging functions as interrupts - the linker
notices that they're present and links them into the interrupt table f
On Tue, Aug 29, 2017 at 3:23 PM, Nick Clifton wrote:
> Hi Jozef,
>
>> As reported in PR80993, enabling lto causes interrupt handlers to be
>> removed. This patch marks interrupt handlers as used, preventing them
>> from being optimized out.
>>
>> If the attached patch is acceptable, I would apprec
Hi Jozef,
> As reported in PR80993, enabling lto causes interrupt handlers to be
> removed. This patch marks interrupt handlers as used, preventing them
> from being optimized out.
>
> If the attached patch is acceptable, I would appreciate if someone could
> commit it for me, as I do not have wr
As reported in PR80993, enabling lto causes interrupt handlers to be
removed. This patch marks interrupt handlers as used, preventing them
from being optimized out.
If the attached patch is acceptable, I would appreciate if someone could
commit it for me, as I do not have write access.
Thanks,
J
