RE: [cc65] New stable release ahead (was: -O bug in 2.13.2)

From: Shawn Jefferson <sjefferson1shaw.ca>
Date: 2012-02-07 21:37:17
I don't think the first item is really worth working on, but the second
could be more useful.  I've always put zeropage variables into an assembly
source file, but I was just thinking, could you use ZEROPAGE in a C source
file and #pragma zpsym and not have to both with assembly source files at
all?  Ideally, cc65 would just realize that the variables are zeropage
addresses from the segment pragmas.

#pragma data-name("ZEROPAGE")
#pragma bss-name("ZEROPAGE")

And testing it with 2.13.9... it works fine. :)



________________________________________
Joseph Rose
Sent: Monday, February 06, 2012 6:57 AM
Subject: Re: [cc65] New stable release ahead (was: -O bug in 2.13.2)

*  How about declaring text literal's segment per-string.  You could use a
#pragma directive similar to the #pragma *seg ().  This will help with
Hidden64 and, when it's available, MemBank128.
*  I want to see explicit __zeropage declarations in C code.  Such,
especially used as pointers, can significantly increase performance.


----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Tue Feb 7 21:40:52 2012

This archive was generated by hypermail 2.1.8 : 2012-02-07 21:40:55 CET