This seems like a tricky extension to deploy to the operating system.
What is the proposed interface for setting GP on application pages? There are
several things that seem plausible to me, and I wondered how far planning has
gotten.
An mmap/mprotect flag?
An ELF program header PT_ARM_BTI (a-la
QEMU Tooling ([VIRT-252])
=
QEMU plugin support ([VIRT-280])
- port my example tools to his Emilio's framework :todo
- there is now a {RFC v2 00/38} Plugin support Message-Id:
<20181209193749.12277-1-c...@braap.org> to review
- tracking regression in [softmmu
Progress:
[VIRT-246 # ARMv8.1-LOR Limited Ordering Regions ]
Merged to target-arm.next.
[VIRT-294 # ARMv8.3-PAuth, Pointer Authentication ]
Posted v2.
Now booting Will's kernel, which properly detects and enables support.
Once that gets to mainline I'll add the prctl to linux-user/.
[VIRT-339
Progress:
* VIRT-65 [QEMU upstream maintainership]
- QEMU 3.1.0 finally released
- sent out a couple of pull requests
- some easy patches fixing more clang warnings about taking the
address of a member in a packed struct
- read through the Memory Tagging extension specification
(and a
[TCWG-1492] Add timeout and retry to git fetches in Linaro ci infrastructure.
[LLVM-505] LLD implement --pic-veneer for AArch32 linux kernel (pr39886)
In upstream review
[LLVM-509] Add support for v6m range extension thunks to LLD
In upstream review
pr34928 fixed undefined weak reference handling f
== Progress ==
GlobalISel support for Thumb2:
# [LLVM-506] G_LOAD, G_STORE
# [LLVM-500] G_ADD, G_SUB, G_MUL, G_AND, G_OR, G_XOR
# [LLVM-516] G_SEXT, G_ZEXT, G_ANYEXT, G_TRUNC
# G_INTTOPTR, G_PTRTOINT
- Committed upstream
# [LLVM-518] Support G_CONSTANT for Thumb
- Started adding tests
== Pla
== Progress ==
* FDPIC
- (GNU-499) GCC: wait for feedback on v4 patches
- (GNU-411) GDB: will try to keep as much as possible in common with frv
* GCC upstream validation:
- reported a few regressions, helped testing some patches
- dealing with some random results, still
- qemu-3.1.0-rc3, memory c
