On 26 May 2014 03:03, Zhenqiang Chen wrote:
Hi Zhenqiang,
> == Issue ==
>
> * None.
>
> == Progress ==
>
> * Investigate PR61220, 61225 and 61278, which are triggered by my
> previous commits. Patches are in review. (9/10)
> * Investigate codes generated by shrink-wrapping interrupt routes. It
>
== 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 Friday
Maxim,
On 24 May 2014 07:24, Maxim Kuvyrkov wrote:
> On May 24, 2014, at 5:10 PM, Maxim Kuvyrkov wrote:
>
>> Hi,
>>
>> I have tried out a prototype of using binfmt_misc, and it does not appear to
>> be a worthwhile solution at this point.
>>
>> Bottom line: with a nice fast multi-core x86 serve
== Progress ==
* Worked on building binary tarballs from Jenkins. (TCWG 383 - 4/10)
* Continuing work on regression test analysis and reporting. (TCWG
448 - 3/10)
- now copying the check.log from make check to toolchain so
tcwgweb.sh can scan it for build errors in the test cases.
== This week ==
- Completed GCC Launchpad bug dispositions [CARD-300][2/10]
- Backported PR61202 - gcc generated invalid sqdmulh instruction
[TCWG-485](2/10)
- Triaged and investigated Launchpad bug 1295738- Unable to find a
register to spill in class 'LO_REGS' [Card 300](3/10)
- Triaged and in
I've been digging through test logs, and for gcc 4.9.1 native x86_64
tests, all the libsanitizer test cases fail to link due to unresolved
symbols from libpthread and libdl. Does anybody know more about this
bug, or care to fix it ? :-) It still exists in gcc trunk.
- rob -
___
Hmmm I only monitor ARM and AArch64 as cross-targets, not x86_64.
It's really suprising that such libs are missing however I do
remember modifying the .spec fragment when I added support for ARM and
prepared the one for AArch64.
Could that have been unnoticed because most people use an old en
