# Progress #
* TCWG-162, Aarch64 non-stop debugging (or displaced stepping). [4/10]
After testing, patches are posted upstream.
* In order to review one c++ debugging patch, learn some C++ abi,
vtable and VTT, etc. Understand gcc dump by -fdump-class-hierarchy.
[3/10]
* Fix GDB cxx build breakage caused by my patch. [1/10]
* Ask the effect of -fstack-check=specific to AArch64 prologue. GDB
needs update. [1/10]
* Misc, email, meeting. [1/10].
# Plan #
* TCWG-162, commit patches if no objections.
* TCWG-387, use libopcodes to decode instructions in GDB.
--
Yao
FYI. This is a parity feature with both PowerPC64 and x86_64. Needed to support GCCgo. Note full gold support is needed too.
---------- Forwarded message ----------
From: pinskia at gcc dot gnu.org <gcc-bugzilla(a)gcc.gnu.org>
Date: Tue, Oct 6, 2015 at 3:30 PM
Subject: [Bug target/67877] New: Split stack needs to be support for AARCH64
To: gcc-bugs(a)gcc.gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67877
Bug ID: 67877
Summary: Split stack needs to be support for AARCH64
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
Target: aarch64-linux-gnu*
To support gccgo better split stack should be implemented.
Connect recovery - [2/10]
Investigate effectiveness of noise-control measures - TCWG-358 [3/10]
* Host node crashed, tried to recover it, failed, started building a new one
Jenkins automation - TCWG-348 [3/10]
* Everything in place up to first interaction with LAVA kvm
* Considered LAVA team's micro-instance proposal
Misc [2/10]
=Plan=
Discuss micro-instance proposal
Work on whatever comes out of discussion
Finish building new host node, get experiments running again
Investigate effectiveness of noise-control measures - TCWG-358 [6/10]
* Finished setup, started running experiments
* Initial data pretty noisy, more runs needed
* Kicked off more runs for week of Connect
Ensure that all critical data is logged - TCWG-349 [1/10]
* Logged a few more variables, tested, merged
* Put down until we have a controlled image build
Misc - [3/10]
* 2 post-connect days off (4/10)
== Progress ==
o Linaro GCC (3/10)
* Backporting armv8-1 support
* Dealing with conflicts
o Misc (3/10)
* Various meetings
* Internal report on Connect
== Plan ==
o Backports
o Releases process tasks
== This week ==
* TCWG-317 - Exploit wide add operations when appropriate for Aarch32 (4/10)
- Patch sent upstream for review
- Fixed some failing tree-ssa testcases by modifying
'check_effective_target_vect_widen_sum_hi_to_si_pattern' to indicate
Aarch32 supports vector widening add
- Fixed length attributes on patterns in neon.md
- Added test cases to ChangeLog
- Debugging failures on -flto and arm big endian
* TCWG-369 - Exploit wide add operations when appropriate for Aarch64 (3/10)
- Fixed some failing tree-ssa testcases by modifying
'check_effective_target_vect_widen_sum_hi_to_si_pattern' to indicate
Aarch64 supports vector widening add
- Debugging tree-ssa test suite failures
* Bugzilla 57195 (mode iterator bug) blocked compiling new pattern (1/10)
- Patch checked in upstream on trunk
* TCWG-77 - Transform end of loop conditions to min_expr (2/10)
- Submitted upstream waiting for final approval
- Merged multiple patterns into one pattern in match.md
- Rewrote test case to work on all targets
* Misc (1/10)
- Conference calls
== Next week ==
- Holiday/vacation
== Progress ==
- 1 day off recovering from travel and 1 public holiday (4/10)
- https://gcc.gnu.org/ml/gcc-patches/2015-07/msg02196.html (1/10)
* Approved patch
* re-based and retesting before committing
- https://gcc.gnu.org/ml/gcc-patches/2015-10/msg00129.html (1/10)
* Found a latent issue while testing patches
* posted a patch for review
- Widening pass (TCWG-547) - 4/10
* Working on review comments
== Plan ==
* Monday public holiday
* Post the revised patch for widening pass
* commit approved patches
== Progress ==
* Monday off (2/10)
* Buildbot (6/10)
- Investigating sanitizer crash in Thumb2+NEON
- Testing IFC6410 with Linaro 15.09
- CPUs good, 1.7GHz on all cores, stable, cool
- Not enough space on local (fast) flash
- USB stick stable, but slow (3h vs 2h on Chrome 2)
- USB disk unstable and slow (power management, etc)
- SATA broken, and slow
* Infrastructure (1/10)
- Discussing LAVA instance in TCWG lab, benchmarks
- Playing with D02: corrupted system, but the machine is *fast*
* Background (1/10)
- Code review, meetings, discussions, general support, etc.
== Plan ==
* More infrastructure meetings
* More buildbot work
* Whatever...