Hello, > I want to report a problem resulting in access to a variable in the > wrong bank. Experienced with Version 2.6.0 #4309 (Jan 19 2007). > To showcase the bug I used a simple dummy.c:
Huh, this SDCC release, revision #4309 is ancient: We are currently at revision #4684, and at least one of the 350+ patches that have been committed since has fixed the banking problems. Try using a recent snapshot, e.g., from http://sdcc.sf.net/snap.php . > Do you think this is a bug or a feature? It probably would be nice to I think it was a bug. > have the bigger then 1 bank sections automatically split but separate > section for each variable is an overkill. And in addition it is obvious The current approach is to have all temporary values (named r0xNNNN) allocated into a single bank while all other, user-defined variables are placed into a section of their own. There are plans to cluster closely related variables into banks according the number of banksels between them, but implementation takes time. In the meantime I might be able to revert to the old behaviour, allocating all variables defined in a .o file into a single section and introduce a new (compiler flag / environment variable / pragma) to select old or new behaviour. Regards, Raphael ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sdcc-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sdcc-user
