Jump to content

Pavel

Administrators
  • Content Count

    1,466
  • Joined

  • Last visited

Everything posted by Pavel

  1. Bug found and fixed in BoostC 1.4 Alpha release. Regards, Pavel
  2. I will try to reproduce this error and if there is one it will be fixed by the next release (or update). Regards, Pavel
  3. Fixed in BoostC 1.4 Alpha release. I also discovered that when 16 bit variable is used inside clear_bit macro compiler generates unoptimized code (8 instructions). This has been changed too (now only 1 instruction is generated). Regards, Pavel
  4. Nice one. Will do by the next release. Regards, Pavel
  5. Preprocessor parses input from left to right and it finds start of a new C comment at the end of this line while you probably look at this line from right to left and see end of C comment there . Add a space in front of '*' and code will compile. Regards, Pavel
  6. You use label with the 'asm' operator incorrectly (see compiler documentation). Your code should look more like: asm{ btfss INTCON,1 goto label_end bsf _trisc,1 bsf _trisc,2 bsf _trisb,5 } asm: label_end asm nop Regards, Pavel
  7. I will add to Dave's reply. You can define pins as Dave described using BoostC compiler. There is no way to define pins in C2C. Regards, Pavel
  8. I tried but couldn't reproduce the problem. The project I tried on is available to download from http://www.picant.com/download/page.zip. If you have a _simple_ sample project that exibits this code page problem please send it to me. Regrads, Pavel
  9. PicAnt and SourceBoost use different registry entries. If you install SourceBoost into a different location it should coexist with PicAnt. You may backup your PicAtn registry entries before SourceBoost installation just in case. regards, Pavel
  10. BoostC 1.3 bug fix release is ready and available to download from http://www.picant.com/c2c/download.html Changes: fix for bank selection at function start; fixed value of literal constants; corrected documentation about pragma DATA useage. Regards, Pavel
  11. I'm not aware of any paging problems in C2C++ compiler. Please send me a project that exibits this error and description how to reproduce it. Regards, Pavel
  12. You are right. I fixed the error in documentation and updated BoostC 1.2 update file. Regards, Pavel
  13. Support for 32 bit data types will be added in final release. Regards, Pavel
  14. You need to use comma after adress. The fromat is: #pragma DATA <addr>, <data>, <data>,... where: <addr> address on dec or hex form <data> data in hex or dec or string form (BoostC 1.2 update includes this info in BoostC help file) Regards, Pavel
  15. BoostC bug fix release is ready and available to download from http://www.picant.com/c2c/download.html Main changes are: fix for shift operations added pragma DATA to set target config word and put user data into eeprom and code memory Regards, Pavel
  16. If you use SourceBoost, BoostC or C2C compilers and like them we ask you to put a phrase about it on your web site. We will even give you a free Extra Plugins license if you do so. Regards, Pavel
  17. Yes it will be possible to use DATA pragma for both configuration word, eeprom data and data in code memory. Regards, Pavel
  18. The problem of placing user data at a certain address has been fixed with '#pragma DATA' directive that will be available in the next release. Regards, Pavel
  19. Implemented and will be available in the next release. Regards, Pavel
  20. Fixed. Fix will be available in the next release. Regards, Pavel
  21. This one has been fixed. Fix will be available in the next release. Regards, Pavel
  22. BoostC has been fixed. Fix will be available in the next update. Regards, Pavel
  23. No it's not. Why do you want to do this? Regards, Pavel
  24. No BoostC doesn't support bit fields. Bit fields generate far too much code even in "big" compilers like gcc. Do other PIC compilers support bit fields? Do they generate efficient code? Regards, Pavel
×
×
  • Create New...