[Bug target/70063] New: msp430 stack corruption for naked functions

: target Assignee: unassigned at gcc dot gnu.org Reporter: awygle at gmail dot com Target Milestone: --- Created attachment 37853 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37853&action=edit A nearly minimal example of code producing the bug When compiling msp4

[Bug target/70063] msp430 stack corruption for naked functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70063 --- Comment #1 from Andrew Wygle --- A quick correction - as my example above accidentally shows, compiling with optimizations isn't a guarantee of avoiding this problem, it just sometimes helps if the arguments are unused, as the optimizer will

[Bug target/70713] New: msp430 interrupt attribute prevents overriding weak symbols

Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: awygle at gmail dot com Target Milestone: --- Because the interrupt attribute in the msp430 port creates a .word directive inside of the generated assembly, thus: test.c: __attribute__

[Bug target/70063] msp430 stack corruption for naked functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70063 --- Comment #3 from Andrew Wygle --- This appears to be fixed in GCC 6.1

[Bug target/80993] New: [msp430] __attribute__((interrupt)) should imply __attribute__((used))

Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: awygle at gmail dot com Target Milestone: --- Enabling link-time optimization on the MSP430 causes any interrupt handlers which are not called directly to be cheerfully eaten

[Bug target/78554] New: Internal Compiler Error in msp430 target with -mlarge, -O{s123}

Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: awygle at gmail dot com Target Milestone: --- When compiling code for an MSP430 using large model (-mlarge) and any optimization above 0, assigning the address of a global variable to

[Bug target/78818] New: msp430 persistent attribute is not applied correctly in some cases

Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: awygle at gmail dot com Target Milestone: --- The MS430 variable attribute "persistent" places variables in a special section .persistent so that they will not be re-init

[Bug target/78838] New: msp430 option -mcode-region=either, -ffunction-sections, and interrupt function attributes cause incorrect section to be created

Version: 6.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: awygle at gmail dot com Target Milestone: --- On the msp430 target, when using -mcode-region with

[Bug target/78849] New: ICE on initialization of global struct containing __int20 array at varasm.c:4968

Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: awygle at gmail dot com Target Milestone: --- The following code (constructor_bug.i) produces an internal compiler error when compiled for the msp430-elf target: # 1

[Bug target/78818] msp430 persistent attribute is not applied correctly in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78818 --- Comment #1 from Andrew Wygle --- Compiling with -mdata-region=either also causes this problem, with variables ending up in either .either.data or .either.bss.