6502/cc65
1
0
Fork 0
mirror of https://github.com/cc65/cc65.git synced 2024-12-23 04:30:10 +00:00
Code Issues Projects Releases Wiki Activity
9ffa2d05e6
cc65/libsrc/cbm510/gettime.s

97 lines
2.2 KiB
ArmAsm
Raw Normal View History

Added _systime for all platforms git-svn-id: svn://svn.cc65.org/cc65/trunk@1510 b7a2c559-68d2-44c3-8de9-860c34a00d81
2002-11-12 22:49:38 +00:00
;
Fixed the system banking in the cbm510 and the cbm610 targets' versions of clock_gettime() and clock_settime(). Their library function calls must run in the execution bank.
2018-08-19 21:12:54 +00:00
; 2009-07-27, Stefan Haubenthal
; 2009-09-24, Ullrich von Bassewitz
; 2018-08-18, Oliver Schmidt
; 2018-08-19, Greg King
Added _systime for all platforms git-svn-id: svn://svn.cc65.org/cc65/trunk@1510 b7a2c559-68d2-44c3-8de9-860c34a00d81
2002-11-12 22:49:38 +00:00
;
Adjusted comments to match actual prototypes.
2018-11-06 10:13:23 +00:00
; int __fastcall__ clock_gettime (clockid_t clk_id, struct timespec *tp);
Added _systime for all platforms git-svn-id: svn://svn.cc65.org/cc65/trunk@1510 b7a2c559-68d2-44c3-8de9-860c34a00d81
2002-11-12 22:49:38 +00:00
;
Systime implementation derived from the cbm610. git-svn-id: svn://svn.cc65.org/cc65/trunk@4227 b7a2c559-68d2-44c3-8de9-860c34a00d81
2009-09-24 21:09:45 +00:00
.include "time.inc"
.include "cbm510.inc"
Removed (pretty inconsistently used) tab chars from source code base.
2013-05-09 11:56:54 +00:00
.include "extzp.inc"
Added _systime for all platforms git-svn-id: svn://svn.cc65.org/cc65/trunk@1510 b7a2c559-68d2-44c3-8de9-860c34a00d81
2002-11-12 22:49:38 +00:00
Replaced _systime with clock_gettime. We want to add the capability to not only get the time but also set the time, but there's no "setter" for the "getter" time(). The first ones that come into mind are gettimeofday() and settimeofday(). However, they take a struct timezone argument that doesn't make sense - even the man pages says "The use of the timezone structure is obsolete; the tz argument should normally be specified as NULL." And POSIX says "Applications should use the clock_gettime() function instead of the obsolescent gettimeofday() function." The ...timeofday() functions work with microseconds while the clock_...time() functions work with nanoseconds. Given that we expect our targets to support only 1/10 of seconds the microseconds look preferable at first sight. However, already microseconds require the cc65 data type 'long' so it's not such a relevant difference to nanoseconds. Additionally clock_getres() seems useful. In order to avoid code duplication clock_gettime() takes over the role of the actual time getter from _systime(). So time() now calls clock_gettime() instead of _systime(). For some reason beyond my understanding _systime() was mentioned in time.h. _systime() worked exactly like e.g. _sysremove() and those _sys...() functions are all considered internal. The only reason I could see would be a performance gain of bypassing the time() wrapper. However, all known _systime() implementations internally called mktime(). And mktime() is implemented in C using an iterative algorithm so I really can't see what would be left to gain here. From that perspective I decided to just remove _systime().
2018-08-15 13:59:11 +00:00
.import pushax, pusheax, tosmul0ax, steaxspidx, incsp1
Removed (pretty inconsistently used) tab chars from source code base.
2013-05-09 11:56:54 +00:00
.import sys_bank, restore_bank
Added clock_settime() for some CBMs. The CIA TOD only stores the time but not the date. Therefore the date set by clock_settime() ist just stored inside the C library for retrieval via clock_gettime(). The "very special" handling of 12AM/PM is based on https://groups.google.com/d/msg/comp.sys.cbm/ysVYSX4AMbc/vHrXCWEhCOUJ saying: ========== 24hr: Wr => Rd => Nx -------------------- 0 : 92 => 12 => 01 <= Switch from 00 to 01 (24-hour notation) 1 : 01 => 01 => 02 2 : 02 => 02 => 03 11 : 11 => 11 => 92 12 : 12 => 92 => 81 <= Switch from 12 to 13 (24-hour notation) 13 : 81 => 81 => 82 14 : 82 => 82 => 83 23 : 91 => 91 => 12 1. column ("24hr"): hour to be tested (decimal) 2. column ("Wr"): hour written to TOD register (BCD) 3. column ("Rd"): hour read from TOD register (BCD) immediately after writing the value in column 2 to see the conversion between AM/PM, if any 4. column ("Nx"): next hour (BCD) after the hour switch ========== Thanks Paul!
2018-08-17 23:13:02 +00:00
.import TM, load_tenth
Replaced _systime with clock_gettime. We want to add the capability to not only get the time but also set the time, but there's no "setter" for the "getter" time(). The first ones that come into mind are gettimeofday() and settimeofday(). However, they take a struct timezone argument that doesn't make sense - even the man pages says "The use of the timezone structure is obsolete; the tz argument should normally be specified as NULL." And POSIX says "Applications should use the clock_gettime() function instead of the obsolescent gettimeofday() function." The ...timeofday() functions work with microseconds while the clock_...time() functions work with nanoseconds. Given that we expect our targets to support only 1/10 of seconds the microseconds look preferable at first sight. However, already microseconds require the cc65 data type 'long' so it's not such a relevant difference to nanoseconds. Additionally clock_getres() seems useful. In order to avoid code duplication clock_gettime() takes over the role of the actual time getter from _systime(). So time() now calls clock_gettime() instead of _systime(). For some reason beyond my understanding _systime() was mentioned in time.h. _systime() worked exactly like e.g. _sysremove() and those _sys...() functions are all considered internal. The only reason I could see would be a performance gain of bypassing the time() wrapper. However, all known _systime() implementations internally called mktime(). And mktime() is implemented in C using an iterative algorithm so I really can't see what would be left to gain here. From that perspective I decided to just remove _systime().
2018-08-15 13:59:11 +00:00
.importzp sreg, tmp1, tmp2
Added _systime for all platforms git-svn-id: svn://svn.cc65.org/cc65/trunk@1510 b7a2c559-68d2-44c3-8de9-860c34a00d81
2002-11-12 22:49:38 +00:00
Systime implementation derived from the cbm610. git-svn-id: svn://svn.cc65.org/cc65/trunk@4227 b7a2c559-68d2-44c3-8de9-860c34a00d81
2009-09-24 21:09:45 +00:00
;----------------------------------------------------------------------------
Added _systime for all platforms git-svn-id: svn://svn.cc65.org/cc65/trunk@1510 b7a2c559-68d2-44c3-8de9-860c34a00d81
2002-11-12 22:49:38 +00:00
.code
Replaced _systime with clock_gettime. We want to add the capability to not only get the time but also set the time, but there's no "setter" for the "getter" time(). The first ones that come into mind are gettimeofday() and settimeofday(). However, they take a struct timezone argument that doesn't make sense - even the man pages says "The use of the timezone structure is obsolete; the tz argument should normally be specified as NULL." And POSIX says "Applications should use the clock_gettime() function instead of the obsolescent gettimeofday() function." The ...timeofday() functions work with microseconds while the clock_...time() functions work with nanoseconds. Given that we expect our targets to support only 1/10 of seconds the microseconds look preferable at first sight. However, already microseconds require the cc65 data type 'long' so it's not such a relevant difference to nanoseconds. Additionally clock_getres() seems useful. In order to avoid code duplication clock_gettime() takes over the role of the actual time getter from _systime(). So time() now calls clock_gettime() instead of _systime(). For some reason beyond my understanding _systime() was mentioned in time.h. _systime() worked exactly like e.g. _sysremove() and those _sys...() functions are all considered internal. The only reason I could see would be a performance gain of bypassing the time() wrapper. However, all known _systime() implementations internally called mktime(). And mktime() is implemented in C using an iterative algorithm so I really can't see what would be left to gain here. From that perspective I decided to just remove _systime().
2018-08-15 13:59:11 +00:00
.proc _clock_gettime
Systime implementation derived from the cbm610. git-svn-id: svn://svn.cc65.org/cc65/trunk@4227 b7a2c559-68d2-44c3-8de9-860c34a00d81
2009-09-24 21:09:45 +00:00
Replaced _systime with clock_gettime. We want to add the capability to not only get the time but also set the time, but there's no "setter" for the "getter" time(). The first ones that come into mind are gettimeofday() and settimeofday(). However, they take a struct timezone argument that doesn't make sense - even the man pages says "The use of the timezone structure is obsolete; the tz argument should normally be specified as NULL." And POSIX says "Applications should use the clock_gettime() function instead of the obsolescent gettimeofday() function." The ...timeofday() functions work with microseconds while the clock_...time() functions work with nanoseconds. Given that we expect our targets to support only 1/10 of seconds the microseconds look preferable at first sight. However, already microseconds require the cc65 data type 'long' so it's not such a relevant difference to nanoseconds. Additionally clock_getres() seems useful. In order to avoid code duplication clock_gettime() takes over the role of the actual time getter from _systime(). So time() now calls clock_gettime() instead of _systime(). For some reason beyond my understanding _systime() was mentioned in time.h. _systime() worked exactly like e.g. _sysremove() and those _sys...() functions are all considered internal. The only reason I could see would be a performance gain of bypassing the time() wrapper. However, all known _systime() implementations internally called mktime(). And mktime() is implemented in C using an iterative algorithm so I really can't see what would be left to gain here. From that perspective I decided to just remove _systime().
2018-08-15 13:59:11 +00:00
jsr pushax
jsr pushax
Systime implementation derived from the cbm610. git-svn-id: svn://svn.cc65.org/cc65/trunk@4227 b7a2c559-68d2-44c3-8de9-860c34a00d81
2009-09-24 21:09:45 +00:00
Fixed the system banking in the cbm510 and the cbm610 targets' versions of clock_gettime() and clock_settime(). Their library function calls must run in the execution bank.
2018-08-19 21:12:54 +00:00
jsr sys_bank
Removed (pretty inconsistently used) tab chars from source code base.
2013-05-09 11:56:54 +00:00
ldy #CIA::TODHR
lda (cia2),y
sed
Fixed 12 AM/PM handling. Midnight is 12 AM and noon is 12 PM (see https://en.wikipedia.org/wiki/12-hour_clock). Therefore we need to subtract 12 hours in exactly those two hours.
2018-08-17 22:13:38 +00:00
tax ; Save PM flag
and #%01111111
cmp #$12 ; 12 AM/PM
bcc @L1
sbc #$12
@L1: inx ; Get PM flag
bpl @L2
Removed (pretty inconsistently used) tab chars from source code base.
2013-05-09 11:56:54 +00:00
clc
adc #$12
Fixed 12 AM/PM handling. Midnight is 12 AM and noon is 12 PM (see https://en.wikipedia.org/wiki/12-hour_clock). Therefore we need to subtract 12 hours in exactly those two hours.
2018-08-17 22:13:38 +00:00
@L2: cld
jsr BCD2dec
Removed (pretty inconsistently used) tab chars from source code base.
2013-05-09 11:56:54 +00:00
sta TM + tm::tm_hour
ldy #CIA::TODMIN
lda (cia2),y
jsr BCD2dec
sta TM + tm::tm_min
ldy #CIA::TODSEC
lda (cia2),y
jsr BCD2dec
sta TM + tm::tm_sec
Fixed the system banking in the cbm510 and the cbm610 targets' versions of clock_gettime() and clock_settime(). Their library function calls must run in the execution bank.
2018-08-19 21:12:54 +00:00
ldy #CIA::TOD10
lda (cia2),y
jsr restore_bank
pha
Replaced _systime with clock_gettime. We want to add the capability to not only get the time but also set the time, but there's no "setter" for the "getter" time(). The first ones that come into mind are gettimeofday() and settimeofday(). However, they take a struct timezone argument that doesn't make sense - even the man pages says "The use of the timezone structure is obsolete; the tz argument should normally be specified as NULL." And POSIX says "Applications should use the clock_gettime() function instead of the obsolescent gettimeofday() function." The ...timeofday() functions work with microseconds while the clock_...time() functions work with nanoseconds. Given that we expect our targets to support only 1/10 of seconds the microseconds look preferable at first sight. However, already microseconds require the cc65 data type 'long' so it's not such a relevant difference to nanoseconds. Additionally clock_getres() seems useful. In order to avoid code duplication clock_gettime() takes over the role of the actual time getter from _systime(). So time() now calls clock_gettime() instead of _systime(). For some reason beyond my understanding _systime() was mentioned in time.h. _systime() worked exactly like e.g. _sysremove() and those _sys...() functions are all considered internal. The only reason I could see would be a performance gain of bypassing the time() wrapper. However, all known _systime() implementations internally called mktime(). And mktime() is implemented in C using an iterative algorithm so I really can't see what would be left to gain here. From that perspective I decided to just remove _systime().
2018-08-15 13:59:11 +00:00
lda #<TM
ldx #>TM
jsr _mktime
ldy #timespec::tv_sec
jsr steaxspidx ; Pops address pushed by 2. pushax
Added clock_settime() for some CBMs. The CIA TOD only stores the time but not the date. Therefore the date set by clock_settime() ist just stored inside the C library for retrieval via clock_gettime(). The "very special" handling of 12AM/PM is based on https://groups.google.com/d/msg/comp.sys.cbm/ysVYSX4AMbc/vHrXCWEhCOUJ saying: ========== 24hr: Wr => Rd => Nx -------------------- 0 : 92 => 12 => 01 <= Switch from 00 to 01 (24-hour notation) 1 : 01 => 01 => 02 2 : 02 => 02 => 03 11 : 11 => 11 => 92 12 : 12 => 92 => 81 <= Switch from 12 to 13 (24-hour notation) 13 : 81 => 81 => 82 14 : 82 => 82 => 83 23 : 91 => 91 => 12 1. column ("24hr"): hour to be tested (decimal) 2. column ("Wr"): hour written to TOD register (BCD) 3. column ("Rd"): hour read from TOD register (BCD) immediately after writing the value in column 2 to see the conversion between AM/PM, if any 4. column ("Nx"): next hour (BCD) after the hour switch ========== Thanks Paul!
2018-08-17 23:13:02 +00:00
jsr load_tenth
Replaced _systime with clock_gettime. We want to add the capability to not only get the time but also set the time, but there's no "setter" for the "getter" time(). The first ones that come into mind are gettimeofday() and settimeofday(). However, they take a struct timezone argument that doesn't make sense - even the man pages says "The use of the timezone structure is obsolete; the tz argument should normally be specified as NULL." And POSIX says "Applications should use the clock_gettime() function instead of the obsolescent gettimeofday() function." The ...timeofday() functions work with microseconds while the clock_...time() functions work with nanoseconds. Given that we expect our targets to support only 1/10 of seconds the microseconds look preferable at first sight. However, already microseconds require the cc65 data type 'long' so it's not such a relevant difference to nanoseconds. Additionally clock_getres() seems useful. In order to avoid code duplication clock_gettime() takes over the role of the actual time getter from _systime(). So time() now calls clock_gettime() instead of _systime(). For some reason beyond my understanding _systime() was mentioned in time.h. _systime() worked exactly like e.g. _sysremove() and those _sys...() functions are all considered internal. The only reason I could see would be a performance gain of bypassing the time() wrapper. However, all known _systime() implementations internally called mktime(). And mktime() is implemented in C using an iterative algorithm so I really can't see what would be left to gain here. From that perspective I decided to just remove _systime().
2018-08-15 13:59:11 +00:00
jsr pusheax
Fixed the system banking in the cbm510 and the cbm610 targets' versions of clock_gettime() and clock_settime(). Their library function calls must run in the execution bank.
2018-08-19 21:12:54 +00:00
pla
Replaced _systime with clock_gettime. We want to add the capability to not only get the time but also set the time, but there's no "setter" for the "getter" time(). The first ones that come into mind are gettimeofday() and settimeofday(). However, they take a struct timezone argument that doesn't make sense - even the man pages says "The use of the timezone structure is obsolete; the tz argument should normally be specified as NULL." And POSIX says "Applications should use the clock_gettime() function instead of the obsolescent gettimeofday() function." The ...timeofday() functions work with microseconds while the clock_...time() functions work with nanoseconds. Given that we expect our targets to support only 1/10 of seconds the microseconds look preferable at first sight. However, already microseconds require the cc65 data type 'long' so it's not such a relevant difference to nanoseconds. Additionally clock_getres() seems useful. In order to avoid code duplication clock_gettime() takes over the role of the actual time getter from _systime(). So time() now calls clock_gettime() instead of _systime(). For some reason beyond my understanding _systime() was mentioned in time.h. _systime() worked exactly like e.g. _sysremove() and those _sys...() functions are all considered internal. The only reason I could see would be a performance gain of bypassing the time() wrapper. However, all known _systime() implementations internally called mktime(). And mktime() is implemented in C using an iterative algorithm so I really can't see what would be left to gain here. From that perspective I decided to just remove _systime().
2018-08-15 13:59:11 +00:00
ldx #>$0000
jsr tosmul0ax
Systime implementation derived from the cbm610. git-svn-id: svn://svn.cc65.org/cc65/trunk@4227 b7a2c559-68d2-44c3-8de9-860c34a00d81
2009-09-24 21:09:45 +00:00
Replaced _systime with clock_gettime. We want to add the capability to not only get the time but also set the time, but there's no "setter" for the "getter" time(). The first ones that come into mind are gettimeofday() and settimeofday(). However, they take a struct timezone argument that doesn't make sense - even the man pages says "The use of the timezone structure is obsolete; the tz argument should normally be specified as NULL." And POSIX says "Applications should use the clock_gettime() function instead of the obsolescent gettimeofday() function." The ...timeofday() functions work with microseconds while the clock_...time() functions work with nanoseconds. Given that we expect our targets to support only 1/10 of seconds the microseconds look preferable at first sight. However, already microseconds require the cc65 data type 'long' so it's not such a relevant difference to nanoseconds. Additionally clock_getres() seems useful. In order to avoid code duplication clock_gettime() takes over the role of the actual time getter from _systime(). So time() now calls clock_gettime() instead of _systime(). For some reason beyond my understanding _systime() was mentioned in time.h. _systime() worked exactly like e.g. _sysremove() and those _sys...() functions are all considered internal. The only reason I could see would be a performance gain of bypassing the time() wrapper. However, all known _systime() implementations internally called mktime(). And mktime() is implemented in C using an iterative algorithm so I really can't see what would be left to gain here. From that perspective I decided to just remove _systime().
2018-08-15 13:59:11 +00:00
ldy #timespec::tv_nsec
jsr steaxspidx ; Pops address pushed by 1. pushax
Added _systime for all platforms git-svn-id: svn://svn.cc65.org/cc65/trunk@1510 b7a2c559-68d2-44c3-8de9-860c34a00d81
2002-11-12 22:49:38 +00:00
Fixed the system banking in the cbm510 and the cbm610 targets' versions of clock_gettime() and clock_settime(). Their library function calls must run in the execution bank.
2018-08-19 21:12:54 +00:00
lda #$00
Replaced _systime with clock_gettime. We want to add the capability to not only get the time but also set the time, but there's no "setter" for the "getter" time(). The first ones that come into mind are gettimeofday() and settimeofday(). However, they take a struct timezone argument that doesn't make sense - even the man pages says "The use of the timezone structure is obsolete; the tz argument should normally be specified as NULL." And POSIX says "Applications should use the clock_gettime() function instead of the obsolescent gettimeofday() function." The ...timeofday() functions work with microseconds while the clock_...time() functions work with nanoseconds. Given that we expect our targets to support only 1/10 of seconds the microseconds look preferable at first sight. However, already microseconds require the cc65 data type 'long' so it's not such a relevant difference to nanoseconds. Additionally clock_getres() seems useful. In order to avoid code duplication clock_gettime() takes over the role of the actual time getter from _systime(). So time() now calls clock_gettime() instead of _systime(). For some reason beyond my understanding _systime() was mentioned in time.h. _systime() worked exactly like e.g. _sysremove() and those _sys...() functions are all considered internal. The only reason I could see would be a performance gain of bypassing the time() wrapper. However, all known _systime() implementations internally called mktime(). And mktime() is implemented in C using an iterative algorithm so I really can't see what would be left to gain here. From that perspective I decided to just remove _systime().
2018-08-15 13:59:11 +00:00
tax
Fixed the system banking in the cbm510 and the cbm610 targets' versions of clock_gettime() and clock_settime(). Their library function calls must run in the execution bank.
2018-08-19 21:12:54 +00:00
jmp incsp1
Added _systime for all platforms git-svn-id: svn://svn.cc65.org/cc65/trunk@1510 b7a2c559-68d2-44c3-8de9-860c34a00d81
2002-11-12 22:49:38 +00:00
.endproc
Systime implementation derived from the cbm610. git-svn-id: svn://svn.cc65.org/cc65/trunk@4227 b7a2c559-68d2-44c3-8de9-860c34a00d81
2009-09-24 21:09:45 +00:00
;----------------------------------------------------------------------------
; dec = (((BCD>>4)*10) + (BCD&0xf))
Removed (pretty inconsistently used) tab chars from source code base.
2013-05-09 11:56:54 +00:00
.proc BCD2dec
Systime implementation derived from the cbm610. git-svn-id: svn://svn.cc65.org/cc65/trunk@4227 b7a2c559-68d2-44c3-8de9-860c34a00d81
2009-09-24 21:09:45 +00:00
Removed (pretty inconsistently used) tab chars from source code base.
2013-05-09 11:56:54 +00:00
tax
and #%00001111
sta tmp1
txa
Systime implementation derived from the cbm610. git-svn-id: svn://svn.cc65.org/cc65/trunk@4227 b7a2c559-68d2-44c3-8de9-860c34a00d81
2009-09-24 21:09:45 +00:00
and #%11110000 ; *16
lsr ; *8
sta tmp2
lsr
lsr ; *2
adc tmp2 ; = *10
adc tmp1
rts
.endproc
Reference in New Issue Copy Permalink