Lines Matching full:tables
13 that maps onto to the region of storage used for those virtual tables. Each
39 The scheme will cause the virtual tables for A, B and C to be laid out
230 The virtual tables will be laid out like this:
259 padding between virtual tables that in many cases aligns address points to
260 a power of 2. Specifically, our padding aligns virtual tables to the next
275 likely to occur if the virtual tables are padded.
277 Forward-Edge CFI for Virtual Calls by Interleaving Virtual Tables
280 Dimitar et. al. proposed a novel approach that interleaves virtual tables in [1]_.
283 address points of the virtual tables are consecutive, thus the validity check of a virtual
287 separate virtual tables, 2) order virtual tables by a pre-order traversal of the class hierarchy
288 and 3) interleave virtual tables.
291 enhancements (more in `Interleave virtual tables`_).
295 Split virtual table groups into separate virtual tables
298 The Itanium C++ ABI glues multiple individual virtual tables for a class into a combined virtual ta…
299 …me, however, can only work with individual virtual tables so it must split the combined virtual ta…
300 …ot require the splitting but it is more efficient when the combined virtual tables have been split.
301 The `GlobalSplit`_ pass is responsible for splitting combined virtual tables into individual ones.
305 Order virtual tables by a pre-order traversal of the class hierarchy
309 For the interleaving scheme, since the combined virtual tables have been split in the previous step,
310 this step ensures that for any class all the compatible virtual tables will appear consecutively.
311 For the old scheme, the same property may not hold since it may work on combined virtual tables.
336 This step will arrange the virtual tables for A, B, C, and D in the order of *vtable-of-A, vtable-o…
338 Interleave virtual tables
342 whole virtual tables in the previously computed order, the interleaving scheme lays out table
343 entries of the virtual tables strategically to ensure the following properties:
360 …g two work lists, one initialized with all the offset-to-top entries of virtual tables in the order
374 Then for each virtual function the algorithm goes through all the virtual tables in the previously …
433 of virtual tables.
720 in the same manner as jump tables for indirect function calls (see above).