[ACTIVITY] week ending Apr. 29 2018
SVE Support ([VIRT-198])
RISU Support for SVE ([VIRT-199])
~
- more tweaking on ASL script while re-generating FP16 tests
[VIRT-199] https://projects.linaro.org/browse/VIRT-199
SVE Reviews
~~~
- started reviewing {PATCH 0/9} target/arm: Fixups for
ARM_FEATURE_V8_FP16 Message-Id:
<20180425012300.14698-1-richard.hender...@linaro.org>
- fixed a couple of other problems testing picked up, see [this
branch]
[this branch] https://github.com/stsquad/qemu/tree/review/rth-fp16-fixes
SoftFloat Bugs ([VIRT-69])
==
- fixed the ARM FP16 corner cases in fcvt
- posted {RFC PATCH} softfloat: re-factor float to float conversions
Message-Id: <20180426154035.16155-1-alex.ben...@linaro.org>
- finish adding support for fcvt to fp-test :todo
[VIRT-69] https://projects.linaro.org/browse/VIRT-69
Upstream Work ([VIRT-109])
==
- catch-up on review queue :todo
- posted {PATCH} linux-user: set minimum uname for RISC-V Message-Id:
<20180424160329.8089-1-alex.ben...@linaro.org>
- posted {PATCH v2} linux-user: set minimum uname for RISC-V
Message-Id: <20180425100218.24785-1-alex.ben...@linaro.org>
- posted {RFC PATCH} hw/core: expand description of null-machine
Message-Id: <20180425153343.24023-1-alex.ben...@linaro.org>
- looks like a better fix is needed
[VIRT-109] https://projects.linaro.org/browse/VIRT-109
Fixing up tests/tcg
~~~
- posted {PATCH v3 00/46} fix building of tests/tcg Message-Id:
<20180424152405.10304-1-alex.ben...@linaro.org>
- series looking pretty good, more comments incoming
Other Tasks
===
- wrote up [ARMv8.2-LPA support] and [ARMv8.2-LVA] cards given current
interest
- Investigate weird QEMU CI OBS build issue :todo
- the OBS build should be failing the RISU tests but isn't, despite
the commit id it reports
[ARMv8.2-LPA support] https://projects.linaro.org/browse/TCWG-1395
[ARMv8.2-LVA] https://projects.linaro.org/browse/TCWG-1396
Completed Reviews [1/1]
===
{PATCH v2 00/17} tcg: tb_lock_removal redux v2
Message-Id: <1522980788-1252-1-git-send-email-c...@braap.org>
~~~
- CLOSING NOTE [2018-04-20 Fri 20:12]
Did some tests and measured small speed increase. Awaiting v3.
Absences
- VNC18 Connect (17th-21st September 2018)
- KVM Forum 2018 (24th-26th October 2018)
Current Review Queue
* {PATCH 0/9} target/arm: Fixups for ARM_FEATURE_V8_FP16
Message-Id: <20180425012300.14698-1-richard.hender...@linaro.org>
* {Qemu-devel} {PATCH 0/9} target/arm: Implement v8.1-Atomics
Message-Id: <20180427002651.28356-1-richard.hender...@linaro.org>
* {RFC PATCH 00/17} reverse debugging
Message-Id: <20180425124533.17182.53165.stgit@pasha-VirtualBox>
* {Qemu-devel} {PATCH v4 0/4} qemu-thread: support --enable-debug-mutex
Message-Id: <20180423053927.13715-1-pet...@redhat.com>
* {Qemu-devel} {PATCH 00/13} Drop compile time limit on number of serial ports
Message-Id: <20180420145249.32435-1-peter.mayd...@linaro.org>
* {Qemu-devel} {PATCH v3 00/18} Translation loop conversion for
sh4/sparc/mips/s390x/openrisc/riscv targets
Message-Id: <1524250517-28032-1-git-send-email-c...@braap.org>
* {PATCH v6 0/3} target/arm: Add a dynamic XML-description of the cp-registers
to GDB
Message-Id: <1524153386-3550-1-git-send-email-abdallah.bouass...@lauterbach.com>
* {RFC PATCH 0/7} avocado: Add acceptance tests parsing the Linux boot console
Message-Id: <20180419164642.9536-1-f4...@amsat.org>
* {PATCH v3 00/15} fp-test + hardfloat
Message-Id: <1522883475-27858-1-git-send-email-c...@braap.org>
* {Qemu-devel} {PATCH V7 0/4} tests: Add migration test for aarch64
Message-Id: <20180228180215.25470-1-...@redhat.com>
* { PATCH v7 00/22} replay additions
Message-Id: <20180227095135.1060.36549.stgit@pasha-VirtualBox>
* {Qemu-devel} {PATCH 0/2} target/sh4: translator loop conversion
Message-Id: <1518751105-17211-1-git-send-email-c...@braap.org>
* {Qemu-arm} {PATCH 0/8} v8m: minor missing regs and bugfixes
Message-Id: <20180205105720.14620-1-peter.mayd...@linaro.org>
* {Qemu-devel} {PATCH} log-for-trace.h: Split out parts of log.h used by trace.h
Message-Id: <20180213140029.8308-1-peter.mayd...@linaro.org>
* {Qemu-devel} {PATCH v5 0/5} coroutine-lock: polymorphic CoQueue
Message-Id: <20180203153935.8056-1-pbonz...@redhat.com>
* {PATCH v3 00/13} Support building with py2 or py3
Message-Id: <20180115102621.9183-1-berra...@redhat.com>
* {PATCH 0/7} docker: update Ubuntu and Fedora images, deprecate old ones
Message-Id: <20180112125000.27256-1-f4...@amsat.org>
* {PATCH v14 0/9} Add ARMv8 RAS virtualization support in QEMU
Message-Id: <1514440458-10515-6-git-send-email-gengdong...@huawei.com>
* {Qemu-devel} {PATCH v3 00/18} Various build-sys and
Re: Linaro Test
> On Apr 27, 2018, at 12:01 PM, andrej.gantv...@wago.com wrote: > > Hello, > > I just noticed that the manifest file of the Linaro gcc-5.5-2017.10 release > under > http://releases.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10/x86_64.arm-linux-gnueabihf-gcc-linaro-5.5-2017.10-manifest.txt > from January, 13th 2018 differs from the original version from October 2017: > the binutils, gdb and abe versions are different. > > Could you please tell me the reason for the changes? > > Thank you very much! Hi Andrej, I don't fully understand. Could you provide both original and new versions of the manifest? Thank you, -- Maxim Kuvyrkov www.linaro.org ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Weekly report for week 17
=== Work done during this GCC week === * stack-protector failure on GCC ARM: need feedback from community + prevent CSE of stack protector's guard first by adding some extra UNSPEC then instead by making all memory accesses involved volatile + write 2 monstro regex (251 & 377 characters respectively) to catch the bug on ARM, Thumb-2 and Thumb-1 + testing and will submit for review later today once I have all test results + discuss raising a CVE * Misc: + Arm meetings + Meeting with ST to discuss how to implement something akin to multilib + spec files for LLVM + Linary syncs + review of "Implement getConstraintRegister for ARM and AArch64" patch by Mikhail Maltsev === Plan for weeks up to 25 === * Paternity leave * Get stack-protector failure fix committed * DSGHACK-25 (Support arithmetic on FileCheck regex variable): finish patch * Start looking into LLVM SPEC optimizations Linaro tickets ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] report week ending 27 Apr
Progress: * VIRT-65 [QEMU upstream maintainership] + 2.12 release kicked out the door; hopefully I can do a bit more actual development work for a bit now... + investigating problems with execute-in-place-from-MMIO-device functionality : the test case (for a Xilinx board model) crashes reliably for me. I cooked up an RFC patch and sent it, but it includes one weird hack and I'm not sure if it's the right approach... + we got a Coverity Scan run through after a couple of months of not having one, and a pile of issues have accumulated. Waded through some of them and flagged them up with the patch submitters who added the code that introduced them. Notes: * QEMU will have not one but two interns working on Cortex-M0 and micro:bit support (one from Google Summer of Code and one from Outreachy) ! * QEMU turns 15 years old this year. To celebrate we plan to make the next release be 3.0 (and perhaps to have birthday cake at KVM Forum?) thanks -- PMM ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
WG: Linaro Test
Hello, I just noticed that the manifest file of the Linaro gcc-5.5-2017.10 release under http://releases.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10/x86_64.arm-linux-gnueabihf-gcc-linaro-5.5-2017.10-manifest.txt from January, 13th 2018 differs from the original version from October 2017: the binutils, gdb and abe versions are different. Could you please tell me the reason for the changes? Thank you very much! Andrej Gantvorg ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
