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
Change MEMTAG_STACK to be d_val, and MEMTAG_GLOBALS to be d_ptr
MEMTAG_STACK should be d_val (a bit to indicate that MTE stack is either on/off), and MEMTAG_GLOBALS should be d_ptr (a pointer offset to a section containing memtag globals descriptors).
This is the way that lld has implemented it, as it's the local semantics (MEMTAG_GLOBALS is a pointer-to-section that needs load bias adjustment, and MEMTAG_STACK is a single bit that enables PROT_MTE on the stack).
This unfortunatly does mean that we diverge from the accepted semantics of odd == d_val, and even == d_ptr, but this seems like the best trade-off as we've shipped a compiler that did the non-spec-but-more-logical thing and shipped binaries to end users. Much better than shipping a whole new set of MEMTAG_GLOBALS_2 and MEMTAG_STACK_2 to fix the mistake.
Found by eugenis@ in https://r.android.com/2765590
In memtagabi readme, be more clear about exceptions to Apache-2.0
This is purely a readibility improvement. Make the exceptions list items, and
add a colon after exceptions, so the readers brain is primed.
get documents ready for 2021q3 release
- for all documents change date and release number of release
- for changed documents, amend the change history table