comparison ToDo @ 165:572aff021627

- file name/layout cleanup, removed "-att" from x64 .S filenames, as unnecessary and also misleading - some "I'm bored"-whitespace-cleanup
author cslag
date Thu, 05 Jan 2017 10:35:12 +0100
parents 164cf1663b7c
children 2fa600ea50e7
comparison
equal deleted inserted replaced
164:2d330a60c44f 165:572aff021627
1 1.0: 1 1.0:
2 ---- 2 ----
3 - make sure all assembly files declare (or are built) by setting the noexecstack flag,
4 compared to translating code with gcc, it's manual for the assembler; this depends on arch
5 support (currently it's only done for linux):
6
7 "When you compile source code normally, gcc takes care of adding the GNU_STACK
8 markings so that the final object code is not marked with an executable stack
9 unless it actually needs it. However, if you compile assembly code, gcc will
10 not automatically add GNU_STACK markings."
11
3 - dyncallback's "stack_cleanup" can be removed from non x86 impls... test if they still work 12 - dyncallback's "stack_cleanup" can be removed from non x86 impls... test if they still work
13 - target a minimum c version, for use with -pedantic, etc.? Right now we use e.g. extensions
14 for anon structs, etc.
4 - the CallVM-free functions are per VTable, however the latter can be changed out 15 - the CallVM-free functions are per VTable, however the latter can be changed out
5 at runtime... which basically changes potentially the deallocator... 16 at runtime... which basically changes potentially the deallocator...
6 same goes for functions setting the mode. think about how to make this safer - currently 17 same goes for functions setting the mode. think about how to make this safer - currently
7 we have a higher flexibility and we need to potentially clean up from the mode we are in, 18 we have a higher flexibility and we need to potentially clean up from the mode we are in,
8 however, this is open to misuse 19 however, this is open to misuse