| 
|
QuoteRef: ammeW6_2001
topics >
all references >
ThesaHelp:
ACM references a-e
ThesaHelp:
references a-b
Topic:
error safe systems
Topic:
dynamic type checking
Topic:
type-safe and secure languages
Topic:
mobile code
Topic:
referential transparency
Topic:
security of remotely executed code
Topic:
static single assignment; SSA
Group:
type checking
Topic:
safe use of pointers
Topic:
range checking
Topic:
run-time assertions
Reference
Amme, W., Dalton, N., von Ronne, J., Franz, M., "SafeTSA: A type safe and referentially secure mobile-code representation based on static single assignment form", Proceedings of the ACM SIGPLAN '01 Conference on Programming Language Design and Implementation (PLDI), Snowbird Utah, ACM SIGPLAN, June 2001, pp. 137-146. Google
abstract ;;Quote: SafeTSA is compact, type-safe mobile code based on static single assignment; safe by construction with referential integrity, type separation, and type check elimination
137 ;;Quote: SafeTSA uses SSA to distinguish unique values of a variable; uses phi-instructions and data flow instead of local variables
137 ;;Quote: SafeTSA guarantees referential integrity by construction; reference in terms of a basic block in the dominator tree
137 ;;Quote: SafeTSA assigns a separate register plane for every type; guarantees type separation without type and range checks
139 ;;Quote: SafeTSA includes safe-ref that cannot be null, and safe-index-arr that cannot be out of range; via runtime checks
ThesaHelp: ACM references a-e (259 items)
ThesaHelp: references a-b (396 items)
Topic: error safe systems (75 items)
Topic: dynamic type checking (43 items)
Topic: type-safe and secure languages (42 items)
Topic: mobile code (14 items)
Topic: referential transparency (26 items)
Topic: security of remotely executed code (22 items)
Topic: static single assignment; SSA (19 items)
Group: type checking (12 topics, 385 quotes)
Topic: safe use of pointers (102 items)
Topic: range checking (20 items)
Topic: run-time assertions (25 items)