You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dearth of standard library functionality in LLVM's SDK at the very least presents the image that the compiler is less far along than it actually is. Quite a bit of the standard library functionality in the SDK that is missing is also rather useful, e.g. the time functions.
Given that LLVM itself has set a goal to provide good pure C versions of all of these routines, through its compiler-rt, llvm-libc, and libc++ subprojects, we should at least attempt to port these to llvm-mos. Whatever we can get working well for the 6502 can be imported into the SDK during its build process via the exsting library merging abstraction.
Given that upstreaming llvm-mos is a distant glimmer, we can make changes to these routines in LLVM to make them suitable for the 6502. This can be guarded by macro flags in the usual way.
The text was updated successfully, but these errors were encountered:
The dearth of standard library functionality in LLVM's SDK at the very least presents the image that the compiler is less far along than it actually is. Quite a bit of the standard library functionality in the SDK that is missing is also rather useful, e.g. the time functions.
Given that LLVM itself has set a goal to provide good pure C versions of all of these routines, through its compiler-rt, llvm-libc, and libc++ subprojects, we should at least attempt to port these to llvm-mos. Whatever we can get working well for the 6502 can be imported into the SDK during its build process via the exsting library merging abstraction.
Given that upstreaming llvm-mos is a distant glimmer, we can make changes to these routines in LLVM to make them suitable for the 6502. This can be guarded by macro flags in the usual way.
The text was updated successfully, but these errors were encountered: