[Bug target/78818] msp430 persistent attribute is not applied correctly in some cases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78818 DJ Delorie changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||dj at redhat dot com Resolution|--- |FIXED --- Comment #4 from DJ Delorie --- Fixed.
[Bug target/78818] msp430 persistent attribute is not applied correctly in some cases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78818 Jozef Lawrynowicz changed: What|Removed |Added CC||jozef.l at mittosystems dot com --- Comment #3 from Jozef Lawrynowicz --- This has been fixed, could someone close this PR please.
[Bug target/78818] msp430 persistent attribute is not applied correctly in some cases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78818 --- Comment #2 from Nick Clifton --- Author: nickc Date: Thu Jun 15 13:38:52 2017 New Revision: 249222 URL: https://gcc.gnu.org/viewcvs?rev=249222=gcc=rev Log: Fix problems with the MSP430 port's handling of persistent data. PR target/78818 gcc * config/msp430/msp430.c (msp430_data_attr): Check that it's possible for a variable to have a section before checking if the section has a name. Set section to.persistent if persistent attribute is set. Warn if .persistent attribute is used on an automatic variable. tests * gcc.target/msp430/pr78818-real.c: New template for tests. * gcc.target/msp430/pr78818-auto.c: New test. * gcc.target/msp430/pr78818-data-region.c: New test. * gcc.target/msp430/pr78818-data-sec.c: New test. * gcc.target/msp430/pr78818-auto-warn.c: New test. Added: trunk/gcc/testsuite/gcc.target/msp430/pr78818-auto-warn.c trunk/gcc/testsuite/gcc.target/msp430/pr78818-auto.c trunk/gcc/testsuite/gcc.target/msp430/pr78818-data-region.c trunk/gcc/testsuite/gcc.target/msp430/pr78818-data-sec.c trunk/gcc/testsuite/gcc.target/msp430/pr78818-real.c Modified: trunk/gcc/ChangeLog trunk/gcc/config/msp430/msp430.c trunk/gcc/testsuite/ChangeLog
[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.