Re: clang-aarch64-sve-vls-2stage workers

Hi Vitaly, Thanks for pointing out the bad buildbot worker. We were already looking into the issue and I have now stopped the worker until it's fixed. Apologies for inconvenience! -- Omair Javaid www.linaro.org On Mon, 1 Apr 2024 at 22:19, Vitaly Buka wrote: > Looks like one wor

Re: LLVM buildbot clang-aarch64-full-2stage

Hi Orlando, Thanks for getting in touch. I have just approved your zorg pull request. Please request Galina Kistanova gkistan...@gmail.com for buildbots restart once you merge your changes to zorg. On Fri, 22 Mar 2024 at 17:25, orlando.hy...@sony.com wrote: > Hi, > > I noticed this address

Re: Flang buildbot workers

/175 https://lab.llvm.org/buildbot/#/builders/191 https://lab.llvm.org/buildbot/#/builders/173 https://lab.llvm.org/buildbot/#/builders/181 PS: http://llvm.validation.linaro.org/ is still showing old builders a patch has been merged so it will be updated soon. Omair Javaid www.linaro.org On Thu

Re: Flang buildbot workers

I just checked there are 160 cores on the machine and all bots are running well above 100%. There has been a master update recently so some bots have changed names meaning and I guess new worker build directories will be formed for all affected. Omair Javaid www.linaro.org On Wed, 23 Jun 2021

Re: Many of your builders are red for long time

> https://reviews.llvm.org/rGb2851aea80e5 . I hope to get windows > >> builders green by end of this week. > >> > >> Hi Galina, > >> > >> linaro-armv8-windows-msvc-01 and -02 are in good shape now: > >> - http://lab.llvm.org:8014/#/wo

Re: GDB: etm traces decoding and breakpoints for arm targets

this helps. -- Omair Javaid www.linaro.org On Mon, 2 Nov 2020 at 15:06, Zied Guermazi wrote: > > hi, > > while testing the implementation in gdb of branch tracing on arm > processors using etm, I faced the the situation where a breakpoint was > set, was hit and then the execut

Re: Please make lldb-aarch64-ubuntu non-flaky, or stop it from sending email / irc pings

Hi Nico, We have investigated lldb-aarch64-ubuntu buildbot's intermittently test failures. They seemed to be triggered by https://reviews.llvm.org/D83904 We have committed a fix https://reviews.llvm.org/D85514 We regret the inconvenience this may have caused. Thanks! -- Omair Javaid

[ACTIVITY] 27 - 31 March 2017

=== This Week === GDB Kernel Awarenes - Kernel Dump setup for ARM [9/10] -- Background study on kdump and try to find working steps for QEMU ARM. -- There is a problem with kdump-tools install script with QEMU -- Tried building kernel for Raspberry Pi2 and Pi3 with kdump, no success so far. --

[ACTIVITY] 20 - 24 Feb 2017

=== This Week === LLDB ARM/AArch64 hardware breakpoints [TCWG-717] [3/10] -- Fixed issues identified during review. -- Investigation of thumb32 vs thumb16 mode selection for arm hw breakpoints. -- Committed upstream. LLDB BUD17 Presentation [6/10] -- Created demos -- Wrote slides Miscellaneous

[ACTIVITY] 13 - 17 Feb 2017

=== This Week === LLDB ARM/AArch64 hardware breakpoints [TCWG-717] [6/10] -- Test on Arm hardware and fix issues. -- Wrote breakpoint command based test-cases for multi-thread tests. -- Wrote RSP packets based test-cases. -- Code clean-up, formatting and re basing to latest code. -- Submit final

[ACTIVITY] 6 - 10 Feb 2017

=== This Week === LLDB ARM/AArch64 hardware breakpoints [TCWG-717] [9/10] -- Submitted AArch64 hardware breakpoint patch for review. -- Updates after upstream comments. -- Added Arm hardware breakpoint support code. -- Testing and debugging of Arm code on android arm device. Miscellaneous

[ACTIVITY] 30 Jan - 3 Feb 2017

=== This Week === LLDB ARM/AArch64 hardware breakpoints [TCWG-717] [9/10] -- Wrote multi-threaded implementation of hardware breakpoints. -- Added thread specific handlers to create hardware breakpoints. -- Basic multi-threaded test application works after some fixes and debugging. -- Committed

[ACTIVITY] 23 - 27 January 2017

=== This Week === LLDB ARM/AArch64 hardware breakpoints [TCWG-717] [6/10] -- Fixed hardware breakpoints routines in LLDB AArch64 register context. -- Code tweaks in NativeProcessLinux/NativeThreadLinux/ProcessGDBRemote -- Hardware breakpoint working with single threaded applications -- Submitted

[ACTIVITY] 16 - 20 January 2017

=== This Week === Investigate LLDB testsuite failures on Pine64 target (AArch32 and AArch64 modes) [TCWG-1012] [4/10] -- Capture tests leaving behind runaway processes, found 3 so far. -- Capture random failures and mark them flakey. ARM/AArch64 hardware breakpoints [TCWG-717] [5/10] -- Code

[ACTIVITY] 09 - 13 January 2017

=== This Week === Monitor LLDB buildbot for minimum down time. [TCWG-712] [1/10] -- LLDB Arm build was broken and then fixed upstream but a buildbot script bug. -- Fixed buildbot script to make sure not every type of build is refreshed after a breakage. Investigate LLDB testsuite failures on

[ACTIVITY] 02 - 6 January 2016

=== This Week === Back from month long holiday had a surgery during this period. Add Pine64 as tester to LLDB buildbot [TCWG-1011] [3/10] -- Configure Pine64 with Ubuntu 16.04 image -- Configure network on Pine64 to be used with LLDB buildbot -- Configure Pine64 for AArch32 mode execution --

[ACTIVITY] 06 - 10 June 2016

=== This Week === Support for watchpoint un-alligned watchpoint addresses on LLDB AArch64 [TCWG-367] [3/10] -- Implementation successful without the need for instruction emulation. -- Watchpoint hit detection fixed with ptrace reporting hit address correctly. -- Used up watchpoint HitAddress

[ACTIVITY] 16 - 20 May 2016

=== This Week === Support for watchpoint un-alligned watchpoint addresses on LLDB AArch64 [TCWG-367] [3/10] -- Made changes to NativeRegisterContext_arm64 to support multiple watchpoint slot for a single watch address. -- Enabled unaligned watchpoints and experimented with resulting false

[ACTIVITY] 09 - 13 May 2016

=== This Week === Enable LLDB testsuite to show zero failures on Hikey 96 Board (AArch64 Linux) [TCWG-231] [4/10] -- Ran multiple builds and testsuite runs to figure out latency issues. -- Investigated remaining failures and submitted appropriate bugzilla bugs. -- Committed xfails upstream.

[ACTIVITY] 18 - 22 April 2016

== Progress == LLDB Chromebook Test Stability [TCWG-563] [3/10] -- Failures reduced to 15 fails and 4 errors after fixing stepping bug. -- Investigated remaining issues some of them are known issues and others will need further investigation. LLDB ARM Thread Stepping Problem [TCWG-566] [5/10]

[ACTIVITY] 11 - 15 April 2016

== Progress == LLDB Buildbot Setup [TCWG-241] [1/10] -- Created a new factory for LLDB buildbots. Halted plan to migrate till turning chromebook build green. LLDB Chromebook Test Stability [TCWG-563] [3/10] -- Investigated some failures some of them were fixed by a systemZ support large patch

[ACTIVITY] 8 - 12 February 2016

== Progress == LLDB development -- Handling aggregate types return values on arm-linux-gnueabihf ABI. Patch review and committed upstream. [TCWG-228] [1/10] -- Debugging of stepping issues on chromebook (arm hard float ABI) [TCWG-230] [2/10] -- Progress on vector return values and aggregate types

[ACTIVITY] 1 - 5 February 2016

== Progress == LLDB development -- Committed patch fixing return value handling on arm-linux-gnueabihf [TCWG-228] -- Finished work on handling aggregate types return values on arm-linux-gnueabihf ABI. [TCWG-228] [5/10] -- Submitted single and double precision handlers for upstream review.

[ACTIVITY] 25 - 29 January 2016

== Progress == LLDB development -- Submitted patch fixing return value handling on arm-linux-gnueabihf [TCWG-228] [5/10] -- float and double types handled in above patch did some more investigation for handling structs [TCWG-228] [2/10] -- Collecting LLDB status data, ran testsuite on different

[ACTIVITY] 18 - 22 January 2016

== Progress == LLDB development -- Debugging of return value related issue coming up on chromebook ARM [TCWG-228] [2/10] -- Setup of Arm testing on AArch64 using chroot on highkey [TCWG-231] [1/10] -- Investigation of failures when setting watchpoint on vector variables [TCWG-231] [4/10]

[ACTIVITY] 11 - 15 January 2016

== Progress == LLDB development -- Triage testsuite failures on AArch64 highkey [TCWG-231] [5/10] -- Triage testsuite failures on chromebook (armel) [TCWG-228] [3/10] Miscellaneous [2/10] -- Meetings, emails, discussions etc. -- Documents preparation for Thailand visa == Plan == LLDB

[ACTIVITY] 9 - 13 November 2015

== Progress == LLDB development -- Root Google Nexus devices and read debug module configuration with kernel module [TCWG-429] [7/10] -- Figure out steps to unlock and root Nexus S -- Figure out steps to build kernel and kernel module for Nexus S -- Tried out lldb watchpoints with custom

[ACTIVITY] 12 - 16 October 2015

== Progress == LLDB development -- Verify LLDB watchpoints on Android Arm and AArch64 targets. [TCWG-405] [4/10] - Ran LLDB testsuite on Nexus5, Nexus 7, Nexus S and Nexus 9 devices. - Started into failing watchpoint tests on all devices. -- Investigate and fix LLDB watchpoints tests that

[ACTIVITY] 7 - 11 September 2015

== Progress == LLDB development -- Progress to add support for un-alinged watchpoints on AArch64 [TCWG-367] [5/10] -- Truncating watched bits wasnt accepted as a solution, will look into issues during connect. -- Trying to figure out a way to use multiple watchpoint slots for a single watchpoint.

[ACTIVITY] 31 August - 4 September 2015

== Progress == LLDB development -- Testing and bug fixing lldb on hikey AArch64 [TCWG-231] [4/10] -- Looking into multi-threaded watchpoint test failures on AArch64 highkey board. -- Fixed watchpoint installation lag and unexpected behaviour. Submitted http://reviews.llvm.org/D12522 --

[ACTIVITY] 17 - 21 August 2015

== Progress == LLDB development -- Testing and bug fixing lldb on hikey AArch64 [TCWG-886] [2/10] -- Looked into watchpoint tests which are still failing after committing watchpoint support and bug fixes. -- Modifications to arm hardware breakpoint and watchpoint support [TCWG-770]

[ACTIVITY] 24 - 28 August 2015

== Progress == LLDB development -- Testing and bug fixing lldb on hikey AArch64 [TCWG-886] [7/10] -- Improve error handling of AArch64 watchpoint code. Submitted, got reviewed and committed http://reviews.llvm.org/D12328 -- Looked into ways to improve watchpoint installation lag.

[ACTIVITY] 3 - 7 August 2015

== Progress == LLDB development -- Testing and bug fixing lldb on hikey AArch64 [TCWG-886] [9/10] -- Debugging of watchpoint test failures and problems with multiple watchpoints. -- Clean-up of AArch64 watchpoint code and fixing watchpoint cache bugs. Miscellaneous [1/10] -- Meetings, emails,

[ACTIVITY] 27 - 31 July 2015

== Progress == LLDB development -- Setup lldb test debug environment for testing failing tests on chromebook. [1/10] -- Debug various lldb hang scnarios on chromebook for armhf support [TCWG-855] [4/10] -- Figure out alternate fix for http://reviews.llvm.org/D11129. [TCWG-855] [3/10]

[ACTIVITY] 06 - 10 July 2015

== Progress == LLDB development -- Debugging problems with process launch and debugserver crash on remote connection. [TCWG-855] [6/10] -- Caught the notorious issue mentioned above fix can be found here http://reviews.llvm.org/D11129. -- Figured arm lldb and lldbserver host builds on

[ACTIVITY] 29 June - 03 July 2015

== Progress == LLDB development [TCWG-855] [8/10] -- Figure out build steps for building cross lldb-server with arm-linux-genueabihf-g++ -- Debugging of lldb-server communication packets for fixing lldb-server armhf crash problem. -- Comparison with androidabi version to figure out missing

[ACTIVITY] 22 - 26 June 2015

== Progress == LLDB development -- Support for running lldb on arm hard float abi targets [TCWG-855] [7/10] -- Built lldb-server for armhf trusty chromebook -- Figured out problem with lldb-server showing up i386-linux-gnu as target triple. -- Verfied load of arm-elf executable and

[ACTIVITY] 11 - 15 May 2015

== Progress == LLDB development -- Submitted and committed AArch64 hardware watchpoint/breakpoint support [2/10] [TCWG-771] -- Submitted Arm hardware watchpoint/breakpoint support [1/10] [TCWG-770] -- Debugged arm watchpoints on Nexus 7 Android device. [2/10] [TCWG-651] Miscellaneous [5/10]

[ACTIVITY] 4 - 8 May 2015

== Progress == LLDB development -- Finished most of work for ARM watchpoints and hardware breakpoints [3/10] [TCWG-770] -- Added hardware breakpoint handlers for AArch64 [1/10] [TCWG-771] -- Debugging for ARM watchpoints not hitting the hardware watchpoint Set/Clear handlers. [3/10] [TCWG-770]

[ACTIVITY] 20 - 24 April 2015

== Progress == LLDB development -- Debugging test code for hardware breakpoint/watchpoint issues on chromebook for ARM LLDB support [4/10] [TCWG-770] -- Wrote native process linux helpers for arm and aarch64 hardware breakpoints [2/10] [TCWG-770] [TCWG-771] -- Fix, test, debug, cleanup and

[ACTIVITY] 13 - 17 April 2015

== Progress == LLDB development -- Some progress on hardware watchpoint support for lldb arm linux. [1/10] [TCWG-770] -- Some progress on hardware watchpoint support for lldb aarch64 linux. [1/10] [TCWG-771] -- LLDB ARM SysV ABI implementation. [4/10] [TCWG-643] - Testing and updates

[ACTIVITY] 6 - 10 April 2015

== Progress == LLDB development -- Patch update, test and re-submission native Linux register context for Arm. [1/10] [TCWG-650] -- Patch update, test and re-submission POSIX register context for Arm. [1/10] [TCWG-755] -- Tested lldb armhf native build on ubuntu utopic, build fine but lacks of

[ACTIVITY] 30 March - 3 April 2015

== Progress == LLDB development -- Completed implementation and submited native Linux register context for Arm upstream [3/10] [TCWG-650] -- Completed implementation and submitted POSIX register context for Arm upstream [3/10] [TCWG-755] -- Fixing LLDB build and dev environment issues [1/10]

[ACTIVITY] 23 - 27 March 2015

== Progress == LLDB development -- Patch submission and build testing LLDB Arm SysV ABI classes [1/10] [TCWG-643] -- Patch submission and build testing LLDB AArch64 SysV ABI classes [1/10] [TCWG-715] -- Implemented native Linux register context for Arm [3/10] [TCWG-650] -- Implemented POSIX

[ACTIVITY] 16 - 20 March 2015

== Progress == LLDB development -- Implemented LLDB Arm SysV ABI classes [3/10] [TCWG-643] -- Implemented LLDB AArch64 SysV ABI classes [3/10] [TCWG-715] -- Started implementation of Arm native register context [1/10] [TCWG-650] -- Figure out steps to run lldb-remote testsuite on Arm and

Re: [ACTIVITY] 9 - 13 March 2015

I am writing them here: https://wiki.linaro.org/WorkingGroups/ToolChain/LLDB Shouldnt these be public? On 17 March 2015 at 15:13, Renato Golin renato.go...@linaro.org wrote: On 17 March 2015 at 00:42, Omair Javaid omair.jav...@linaro.org wrote: -- Written wiki pages for LLDB developer

[ACTIVITY] 9 - 13 March 2015

== Progress == LLDB development -- Got lldb-server executable running on aarch64 target but debug connection not working [1/10] [TCWG-640] -- Got lldb-server executable running on arm target [1/10] [TCWG-641] -- Started collecting missing pieces for arm lldb linux run control support [2/10]

[ACTIVITY] 23 - 27 Feburary 2015

== Progress == LLDB development -- Some code sniffing and created JIRA cards with some task estimation [2/10] -- Trying AArch64 cross build and update howto [1/10] -- Trying Arm cross build and update howto [2/10] GDB patch updates and test cases for ARM record-replay instruction

[ACTIVITY] 16 - 20 January 2015

== Progress == LLDB development -- LLDB Call graph analysis for understanding some development nits [1/10] -- Trying out LLDB server arm and aarch64 cross compilation. [2/10] -- List down arm-lldb task list with some debugging [2/10] Miscellaneous [1/10] -- 96board setup Holiday [4/10]

[ACTIVITY] 12 - 16 January 2015

== Progress == LLDB vs GDB investigation [TCWG-583] [2/10] Configuration of GDB AArch64 remote testing with juno. [1/10] GDB AArch64/ARM/X86 native/remote testing and comparison result compilation. [4/10] Investigate some record-replay testsuite failures on d01. [2/10] Miscellaneous [1/10]

[ACTIVITY] 1 - 5 December 2014

== Progress == QEMU kernel debugging setup [5/10] [TCWG-568] -- Setup arm Linux kernel debugging to debug watchpoints GDB with cygwin build/testing process [2/10] -- Figured out GDB build and test procedure on cygwin. Miscellaneous [3/10] -- Meetings, Emails etc -- Hong Kong visa

[ACTIVITY] 24 - 28 November 2014

Apology for sending this out late. == Progress == Debugging ARM gdb watchpoint failures [4/10] [TCWG-567] -- Prepared a testsuite patch for unsupported tests on ARM -- Investigation of other failures due to watchpoints installation rejected through ptrace interface. QEMU kernel debugging

[ACTIVITY] 10 - 14 November 2014

== Progress == Environment setup, installations, board setup etc [4/10] -- Prepared a local dev machine to work with in absence of lab. -- Prepare panda board for gdb on android testing. -- Figure out SSH failure issues with gdb testsuite runs. -- Try out foundation model for android

Re: [Question] Should gdb client query FP registers even if gdb server does not report having org.gnu.gdb.aarch64.fpu feature?

:51, Omair Javaid omair.jav...@linaro.org wrote: Have you implemented a qXfer packet response if not you can do so to use xml description provided by target. Here is a gdb help link that describe how to client can query target.xml. https://sourceware.org/gdb/onlinedocs/gdb/Retrieving

Re: [Question] Should gdb client query FP registers even if gdb server does not report having org.gnu.gdb.aarch64.fpu feature?

On 7 November 2014 02:27, Qu, Strong stro...@qti.qualcomm.com wrote: Hello, We have implemented gdb server in one of our project and we are using Linaro aarch64-none-elf-gdb.exe as gdb client. Our gdb server will response to packet 'qXfer:features:read:target.xml:0,fff' with a xml file

Re: [Question] Should gdb client query FP registers even if gdb server does not report having org.gnu.gdb.aarch64.fpu feature?

, I added some code in our code to return the value of fpsr and fpcr to make the gdb client happy. Regards, Strong -Original Message- From: Omair Javaid [mailto:omair.jav...@linaro.org] Sent: Monday, November 10, 2014 3:30 AM To: Qu, Strong Cc: linaro-toolchain@lists.linaro.org

[ACTIVITY] 27 - 31 October 2014

== Progress == GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] [3/10] -- Investigate arm hardware debugging capabilities in linux kernel. ARM/AArch64 GDB testsuite failures investigation [TCWG-507] [4/10] Trying out patches that add support for gdbserver catch vfork/fork [TCWG-507]

[ACTIVITY] 20 - 24 October 2014

== Progress == Further progress on GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] [6/10] -- Debugging and trying out some code enabling tracepoints in gdbserver -- Research on past tracepoint patches and x86 vs arm architecture comparison ARM/AArch64 GDB testsuite failures

Re: Q about using AArch64 gdb with target running in AArch32 state

On 21 October 2014 12:51, Peter Maydell peter.mayd...@linaro.org wrote: On 17 October 2014 16:28, Qu, Strong stro...@qti.qualcomm.com wrote: For our use case, we are running the gdb client at early state of boot. So the ARMv8 target might be running into any EL and into either AArch64 or

[ACTIVITY] 13 - 17 October 2014

== Progress == Catch up with work after return from Eid ul Adha and Annual Holidays [7/10] * Hong Kong visa application * UPS repairs and office cleanup * Catching up with work, gdb roadmap and open/running cards. * Emails/Patch scrolling/Meetings etc * Sick day off on Monday GDB

[ACTIVITY] 1 - 5 September 2014

== Progress == Debug KGDB with gdb for testing [4/10] LCU14 slides preparation and study for presentation. [2/10] Miscellaneous [4/10] * Configure to use hackbox to test aarch64 gdb remote configs * Retrieve gdb test results in different configurations. * Emails/Patch scrolling/Meetings

[ACTIVITY] 25 - 29 August 2014

== Progress == Arm gdb record-replay pending patches up-streaming [3/10] * Update, test and resubmit patches AArch64 gdb record-replay patches up-streaming [3/10] * Update, test and resubmit patches Miscellaneous [4/10] * Configure git for replying to previous patch submission using send

[ACTIVITY] 11 - 15 August 2014

== Progress == Arm gdb record-replay bug fix [4/10] [TCWG-314] * Testing of all patches on x86 and arm machines. * Patch submission upstream after sync up with latest gdb trunk. AArch64 gdb record-replay bug fix [3/10] [TCWG-503][TCWG-498] * Debugging of testsuite failures with apm and

[ACTIVITY] 4 - 8 August 2014

== Progress == BeagleBoard and Pandaboard setup for gdb testing [3/10] * Deployed debian linux on both boards * Installation of required packages for gdb testing * Run gdb native tests on Beagleboard, Pandaboard and Chromebook Arm gdb record-replay bug fix [6/10] [TCWG-314] * Applied

[ACTIVITY] 18 - 25 July 2014

== Progress == GNU Tools Cauldron * Some useful corridor meetings with various GNU tools developers and maintainers. TCWG Sprint [8/10] * Got to meet the team and discuss TCWG roadmap. * Some useful howtos specially back porting and patch review howtos. * Sprint with ARM and useful

[ACTIVITY] 28 July - 1 August 2014

== Progress == BeagleBoard and Pandaboard setup for gdb testing [1/10] * Got both alive and working with minimal os * Trying ubuntu prebuilt binaries didnt work. Out of office to get internet fixed and buy accessories for boards. [1/10] Eid Public Holidays in Pakistan from 29th July till

[ACTIVITY] 7 - 11 July 2014

== Progress == * Testing and Analysis of testsuite failures in arm-linux-gdb [TCWG-509] [6/10] -- Run ARM GDB testsuite on local chromebook, remote chrombook and pandaboards. -- Investigation of failures on arm. * AArch64 GDB handling of functions with empty prologue. [TCWG-504] [1/10] --

[ACTIVITY] 14 - 18 July 2014

== Progress == * On Holiday from 14th to 17th July 2014. * Travel to Cambridge to attend TCWG Sprint and GNU Tools Cauldron on Friday 18th July. == Plan == * Attend GNU Tools Cauldron 18th to 20th July. * Attend TCWG Sprint 21st to 24th July. * Friday 18th July return back after attending

[ACTIVITY] 30 June - 4 July 2014

== Progress == * AArch64 GDB reverse watchpoints issue. [TCWG-503] [4/10] -- Found a new fix in generic process record implementation. Testing stalled by too many 2500 failures seen on arm-linux-gdb in general and some 850 record/replay implementation. * AArch64 GDB handling of functions with

[ACTIVITY] 23 - 27 June 2014

== Progress == * AArch64 GDB reverse watchpoints issues. [TCWG-503] [6/10] -- Proposed a fix which failed testing now working on an alternate fix in gdb process record target implementation. * Further progress on AArch64 GDB handling of functions with empty prologue. [TCWG-504] [2/10] --

[ACTIVITY] 16 - 20 June 2014

Sorry for sending this late this week. == Progress == * Ran gdb testsuite on arm and x86. Investigated failures on arm-native-gdbserver config. [2/10] * Investigate shared library gdb test failures with dejagnu on remote connections. [TCWG-504] [2/10] * Debug AArch64 GDB reverse watchpoints

[ACTIVITY] 09 - 13 June 2014

== Progress == * GDB arm v8 record/replay -- Investigated prologue analysis and stepping issues. [3/10] [TCWG-484] -- Updates to JIRA cards. -- Updates to patches stalled till next week. * GDB arm v7 record/replay -- Prepare SIMD instruction recording support patches for re submission.

[ACTIVITY] 02 - 06 June 2014

== Progress == * GDB arm v8 record/replay -- Fixed issues showing up when building code with default optimization. [TCWG-484] [3/10] -- Fixed failures in until-reverse test cases. [TCWG-484] [1/10] -- Investigation of failures in watchpoint-reverse and solib test cases. [TCWG-484] [2/10]

[ACTIVITY] 26 - 30 May 2014

== Progress == * GDB arm v8 record/replay -- Support for recording advance SIMD load store instructions. [TCWG-403] [4/10] -- Code cleanup and patch creation. [2/10] -- Investigation of patches failing in native configuration. [TCWG-484] [2/10] * Miscellaneous -- Sick day off on Monday

[ACTIVITY] 19 - 23 May 2014

== Progress == * GDB arm v8 record/replay -- Completed implementation of system call recording [TCWG-409] [4/10] -- Support for recording A64 Loads and stores [TCWG-409] [2/10] -- Bug Fixing to reduce failures in gdb.reverse testsuite [TCWG-484] [2/10] * Miscellaneous -- Day off on

[ACTIVITY] 5 - 9 May 2014

== Progress == * GDB arm v8 record/replay: core files issue [TCWG-451] [6/10] -- Add bfd support for missing aarch64 core file handlers. -- Added regset caching functions for aarch64 linux gdb. * GDB arm v8 record/replay: Support for recording A64 Data processing - Floating point

[ACTIVITY] 28th April - 2nd May 2014

== Progress == * GDB reverse debugging on aarch64 -- Further progress on decoding of aarch64 load store instructions. [TCWG-401] [1/10] * Investigated and progressed towards fix for GDB unable to read core files [TCWG-451] [6/10] * Public Holiday on 1st May [2/10] * Miscellaneous [1/10] --

[ACTIVITY] 21 - 25 April 2014

== Progress == * GDB reverse debugging on aarch64 -- Complete decoding of aarch64 data processing immediate instructions. [TCWG-399] [1/10] -- Complete decoding of aarch64 data processing register instructions. [TCWG-402] [1/10] -- Completed decoding of aarch64 exception and system

[ACTIVITY] 14 - 18 April 2014

== Progress == * GDB reverse debugging on aarch64 -- Scored through a64 instruction set details. [1/10] -- Completed testing and implementation of all basic structures. [TCWG-398] [1/10] -- Started decoding aarch64 load store instructions for recording. [TCWG-401] [2/10] -- Completed

[ACTIVITY] 7 - 11 April 2014

== Progress == * GDB reverse debugging on aarch64 [6/10] [TCWG-398] -- Setup development tree and debug environment. -- Verified generic reverse debugging implementation aarch64. -- Implemented main function stubs to catch instruction for decoding and recording. * Work on gdb testing

[ACTIVITY] 31 March - 4 April 2014

== Progress == * Work on gdb testing utility [TCWG-96] [8/10] -- Support to run native and native-gdbserver test via ssh on remote machines like arm-linux. -- Bug fix and test gdb testing utility by running it various configurations. -- Update wiki page with testing utility and how to use

[ACTIVITY] 17 - 21 March 2014

== Progress == * Add support for fork/vfork/exec events/catchpoints in remote gdbserver [TCWG-263] [4/10] -- Debugged catchpoint code and reviewed gdbserver implementation for events. -- Still require a lot of code understanding before actual implementation can start. * Wrote a script that

[ACTIVITY] 10 - 14 March 2014

== Progress == * Get started with Aarch64 GDB testing and development process using foundation model. [6/10] [CARD-1115] -- Figured out steps for running gdb in remote mode using foundation model. -- Wrote a wiki page with steps on development process, still in progress. -- Completed a gdb

[ACTIVITY] 23 - 28 Feburary 2014

== Progress == * Completed testing and submitted patches upstream. [TCWG-251] [TCWG-252] [1/10] * Travel to capital Islamabad for Macau visa follow up. [3/10] * Shifting to new office space and setting up office [6/10] == Plan == * Study aarch64 code and create task breakdown for

[ACTIVITY] 10 - 14 Feburary 2014

== Progress == * Updated, tested and re-submitted patch for arm native watchpoint/hwbreak rework. [2/10] * Updated, split-up and tested patches for process record ASIMD, VFP etc support. [TCWG-251] [TCWG-252] [3/10] * Tried setting up gdb for aarch64, no luck yet. [TCWG-389] [1/10] *

[ACTIVITY] 3 - 7 Feburary 2014

== Progress == * Short week: Public holiday on Wednesday 5th Feburary 2014. [2/10] * Ran gdb testsuites for arm and x86 (native + remote) with all in progress patches applied. [1/10] * Investigated and triaged arm only failures. [2/10] * Investigated gdb.dwarf2/implptr-64bit.exp failure and

Re: kernel support for cortex A8 hardware watchpoints

On 5 February 2014 19:24, Marc Kleine-Budde m...@pengutronix.de wrote: On 02/04/2014 02:49 PM, Ulrich Weigand wrote: Marc Kleine-Budde m...@pengutronix.de wrote on 04.02.2014 00:59:12: I'm on a freescale mx53 (single core, cortex a8) and trying to find a nasty problem in our $CUSTOMER's

[ACTIVITY] 27 - 31 January 2014

== Progress == * Fixed remaining issues in rework of hwbreakpoint and watchpoint implementation for arm native targets. Tested and submitted patch. [TCWG-177] [8/10] * Installation and Setting up of new desktop machine. [2/10] == Plan == * Run testsuites to see current status of arm gdb. *

[ACTIVITY] 20 - 24 January 2014

== Progress == * Implemented per process hwbreakpoint and watchpoint cache for arm native targets. Also added a reference count for per thread hardware breaks. [TCWG-177] [7/10] * Travelled to Islamabad for Macau visa application. [3/10] == Plan == * Continue work on forking/vforking hardware

[ACTIVITY] 13 - 17 January 2014

== Progress == * Implement fork over HW breaks support for arm native targets. [TCWG-177] [6/10] * ARM Process Record: - All patches accepted and upstream. - Spent time making changes to VFP, SIMD etc patch. [2/10] - Configuration and Git ssh setup for gdb commit rights . [1/10] * Submitted a

[ACTIVITY] 6 - 10 January 2014

== Progress == * ARM Process Record: - Follow up on patches, almost all patches accepted. [0.5/10] - Got GDB committ rights and set up git for pushing patches. [0.5/10] * Spent time to read through fortran functions prologue to find a new fix for TCWG-267. [1/10] * Initial investigation of

[ACTIVITY] 30 December 2013 - 3rd January 2014

== Progress == * ARM Process Record: [TCWG-336] [TCWG-338] [TCWG-339][TCWG-317] [TCWG-315] - Configured and learnt to use git format-patch and git send-email. [1/10] - Incorporated and tested changes suggested by maintainers in previous arm process record patches. [2/10] - Created a new patch

[ACTIVITY] 23 - 27 December 2013

== Progress == * ARM Process Record made the changes pointed out in maintainers comments. [3/10] [TCWG-336] [TCWG-338] [TCWG-339] - Put the new bug fixes patches on hold as they can be sent in the same series.[TCWG-317] [TCWG-315] * Time off for setting up new office space. [4/10] - Found a good

[ACTIVITY] 16 - 19 December 2013

== Progress == * Debugged and Fixed process record memory corruption problem. [TCWG-315][TCWG-317][8/10] * Sick Time off [2/10] == Plan == * Send patches for bug fixes and look into remaining arm-native gdb issues. * Respond to maintainer's suggestion on process record patches. * Public

[ACTIVITY] 2 - 6 December 2013

== Progress == * Updated, tested and submitted new patches for a couple of gdb testsuite failure on arm. [TCWG-269] [TCWG-34] [1/10] * Performed GDB git repository testing suite results comparison: [TCWG-34] [2/10] Compared results and prepared googldocsheets for the following: arm-native Vs

[ACTIVITY] 25 - 29 November 2013

== Progress == * Investigated remaining testsuite failures in ARM process record/replay. * Tested VFP, SIMD and other advance instruction types recording. * Ran GDB testsuite in various configurations on gdb7_6_1 code base and latest git repo. * Learnt some prologue and epilogue analysis

[ACTIVITY] 18 - 22 November 2013

== Progress == * GDB ARM Process Record: - Completed work on arm process record Advance SIMD, vfp and coprocessor instruction recording. - Submitted initial patch for SIMD. VFP and coprocessor instruction decoding. - Resubmitted previous patches after incorporating suggestions. - Resolved patch

[ACTIVITY] 11 - 15 November 2013

== Progress == * Wrote ARM and Thumb stub handlers for simd, vfp and coprocessor instruction recording. * Read documentation on VFP and Neon register set to figure out a register recording method. * Follow up on upstream patches. * Investigating a un-handled instruction test suite failure in

[ACTIVITY] 21 - 25 October 2013

== Progress == (TCWG-266), (TCWG-270), (TCWG-250), (TCWG-280) and (TCWG-288) * Arm process record: - Created Patches for all fixes and features. - Performed testing in arm native and remote configuration. - Performed regression testing on arm and x86. - Submitted all fixes in three patch series.

[ACTIVITY] 14 - 18 October 2013

== Progress == * Short week Hujj and Eid-Al-Adha Public Holidays in Pakistan 15-17 October 2013. (TCWG-280) ARM GDB Process Record Syscall support: * Performed testing with all fixes incorporated and debugged failures in remote configuration. == Plan == (TCWG-266), (TCWG-270), (TCWG-250),

  1   2   >