Am 26.06.2012 13:12, schrieb Peter Bigot: >> According to >> http://mspgcc.sourceforge.net/manual/x1028.html >> READ_SR() should return the content of status register r2, however. When >> used, msp430-gcc will returns >> >> error: called object '__read_status_register()' is not a function > > While I agree this is probably a bad choice, turns out it's the manual > that's wrong. READ_SR and READ_SP have been defined as macros that > are not function-like since their introduction in 2001. It would not > be appropriate to change that now. > > Peter >
Did I understand you right: The manual is wrong and should quote READ_SR instead of READ_SR()? I wasn't used to errors in system headers, and was digging manuals, google and my code for hours, until I decided to look into the system headers. It wasn't obvious to find there, too. That wasn't fun at all and messed up my day. I thought this one-liner could save a lot of stress for other beginners like me. But: lessen learned ;) Bests Simeon -- M.Eng. Simeon Felis Fakultät Elektro- und Informationstechnik Laboratory for Safe and Secure Systems, LaS3 - a software engineering discipline (www.las3.de) Seybothstrasse 2 P.O. 12 03 27 93025 Regensburg Germany FON: +49 (0)941 / 943 9823 MOB: +49 (0)176 / 2323 8962
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
