Hi!
On 26.01.2011 02:40, Michael Hope wrote:
On Wed, Jan 26, 2011 at 3:54 AM, Peter Maydell peter.mayd...@linaro.org
wrote:
Christophe Lyon from ST has kindly released a large
set of test cases of Neon intrinsics:
http://gitorious.org/arm-neon-tests/arm-neon-tests
For the record
== Progress ==
* Started Linaro ramp up process
* Lots of admin, PC setup, Linaro docs reading
* Still unable to make bzr work. Investigating proxy restrictions.
* Started working on constant vec permute operation for the vext
instruction
* Still some pending internal work
== Next week
* Out of
== Progress ==
* Out of office Friday 17
* Attended Virtual Connect sessions:
* Vectorization
* PGO/LTO: provided benchmarking results on Webkit computed in ST last
year.
* At last managed to have bzr working
* Prepared a patch for constant vec permute operation for the vext
instruction
== Progress ==
* Validation of my vext patch in big-endian mode proved that proper
support would be non-trivial.
Spent a lot of time writing a self-testing executable test, which
works in both big and little endian modes.
Posted an updated patch which makes no optimization in big-endian.
== Progress ==
* Discussed big-endian patches for vext tests: careful review of the
specification is required and this patch might actually expose GCC
bugs in big-endian/Neon.
* builtin_bswap16:
* Posted 2 implementations of the generic patch for
(x8)|(x8). The 2nd one looks OK, but I
== Progress ==
* builtin_bswap16:
* patch to catch (x8)|x8) committed upstream after confirmation
it was OK by PowerPC guys.
* backporting of builtin_bswap16 for ARM to Linaro/4.7: one of the
tests fails. Trying to isolate the trunk change that would make is
pass.
* useful
== Progress ==
* builtin_bswap16:
* Backported missing patch from thunk to Linaro/4.7. One test still
failing in the hard-float + thumb configuration because it forces
armv6 and results in a unsupported configuration: vfp-1 + hard-float.
Resumed discussion about a fix I proposed 3 weeks ago.
*
armv6 and results in a unsupported configuration: vfp-1 + hard-float.
s/vfp-1/thumb-1/
Christophe
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
== Progress ==
* PGO/hot-cold partitioning/Spec2k:
* Debugging why 254.gap is causing an ICE.
* Connect preparation:
Still preparing a temporary laptop
* Internal stuff
== Next ==
* Connect
___
linaro-toolchain mailing list
== Progress ==
* Started working on Turn off 64 bits Bitops in Neon in GCC blueprint.
* branch review for aarch64-4.7 merge.
A lot of time wasted due network instability making it difficult to
checkout a GCC branch from launchpad/bzr.
* Internal support for infrastructure problems.
* Resumed
== Progress ==
* Turn off 64-bits bitops in Neon: initial implementation under
benchmarking.
Currently it modifies the handling of: add, sub, and, or, xor, shifts,
not. In some case the generated code is quite larger, so it will careful
benchmarking.
* Started looking at disable peeling
== Progress ==
* Turn off 64-bits bitops in Neon: patch proposed upstream after
positive benchmarking.
Re-submitted after request to add testcases and documentation for
the new option.
* Disable peeling: running benchmarks with peeling completely disabled
to see the impact.
* PGO/hot-cold
== Progress ==
* Turn off 64-bits bitos in Neon: Ping-ed patch proposal.
* Disable peeling: benchmarks show good results; sent a proposal
upstream to discuss preliminary implementation needed testsuite
modifications.
* builtin_bswap16 backport to linaro-4.7: need to investigation an
unexpected
More information on Linaro GDB is available at:
https://launchpad.net/gdb-linaro
Christophe Lyon
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
== Progress ==
* gdb-linaro-7.5-2012.12 release
- Updated wikis about gdb sources import from upstream and about
gdb-linaro release
- still some trouble with infrastructure to achieve the release
* 64-bits ops in Neon: no news from upstream
* disable-peeling: upstream advice is to enable tune
== Progress ==
* 64-bits ops in Neon: pinged patch proposal.
* disable peeling/vectorzer cost model: initial benchmarking done wth
cost-model on (now default). Received some results with cost model
off, waiting for spec2k.
* started looking at smin-umin idiom patch from Ramana. Rebased and
== Progress ==
* 64-bits ops in Neon: pinged patch proposal.
* vectorizer cost model: received results from spec2k. Prepared
initial tuning to submit to benchmarking again.
* smin-umin: tests OK, benchmarks ran, but did not generate the diff
over a valid ancestor. I didn't make the manual
== Progress ==
* 64-bits ops in Neon: waiting for upstream.
* vectorizer cost model: initial activation with unaligned load/store
cost equal to aligned ones; benchmarking shows no significant
difference.
* smin-umin: a few benchmarks show a few unexpected regressions (10-15%).
* setting up spec2k
== Progress ==
* 64-bits ops in Neon: No news from upstream.
* vectorizer cost model: added possibility to tune the problem by
processor type.
* smin-umin: regression actually caused by a previous patch brought
when merging bswap16 support. Investigation on-going.
* managed to run spec2k on local
== Progress ==
* 64-bits ops in Neon: upstream accepted the patch for gcc-4.9-stage1
* smin-umin: several benchmarks runs necessary to confirm that the
generic patch I suspected actually caused the regression. However, it
also brings improvements in other benches (office-type).
* looked at
I'd say that adding
-L/opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux/arm-linux-gnueabihf/lib
is unnecessary as gcc's driver should be able to find its own
libraries.
Regarding your problems with ffmpeg, I'm sorry that I don't know how
cmake works, but after spending some time
The Linaro Toolchain Working Group is pleased to announce the 2013.02
release of both Linaro GCC 4.7 and Linaro GCC 4.6.
Linaro GCC 4.7 2013.02 is the eleventh release in the 4.7 series. Based
off the latest GCC 4.7.2+svn195745 release, it includes ARM-focused
performance improvements and bug
- therefore, you should add ffmpeg to OpenCV, maybe using the 3rdparty
directory, but I don't know how it is supposed to be used
I too don't know. Then Cross compiling is not so simple like this:
http://processors.wiki.ti.com/index.php/Building_OpenCV_for_ARM_Cortex-A8
this does not cover
== Progress ==
* smin-umin: spawned build jobs for gcc-trunk with 'coalesce-vars'
patch reverted (from A.Oliva), so that I can then run benchmarks to
compare its effect with the one observed on gcc-4.7.
* libasan: thanks to Peter, I am able to run sample programs under
qemu. Ran GCC testsuite,
== Progress ==
* smin-umin: waiting for benchmark results with 'coalesce-vars' patch
reverted on trunk.
* libsanitizer: its backtrace printing facility relies on unwinding
info not present by default in binaries. Adding -funwind-tables
improves the results in GCC testsuite.
There is still an
Short week...
== Progress ==
* Catch up on internal tasks / email that piled up during holidays + Connect
* Resumed work on disable-peeling:
- local benchmarking on snowball
- restarting benchmarks via cbuild for an additional check
== Next ==
* Check benchmark results on disable-peeling
*
== Progress ==
* Disable-peeling:
- benchmarked locally on snowball. Observed a few regressions in spec2k.
To be analyzed and confirmed with the results from cbuild.
- patched cbuild to work-around a bzr bug which prevented these jobs
from being spawned.
* Libsanitizer: sent patch
== Progress ==
* Disable-peeling:
- Still waiting for the results from cbuild. Because of many merges
(pre-release week), there are a lot of jobs in the queue :-(
* Libsanitizer:
- tried to understand why isatty(2) returns true when executing the
testsuite via qemu.
* Neon intrinsics codegen:
Could you post the full command-line leading to this error?
Did you try to add -fPIC as suggested?
Christophe.
On 18 April 2013 09:53, Marius Cetateanu m...@softkinetic.com wrote:
Hi,
Some time ago I had some problems linking my project libraries for
Android using the Linaro toolchain
Short week (3 days)
== Progress ==
* Disable-peeling: got results vs reference, shared with team.
* Revert-coalesce vars: got results vs reference, showing regressions.
* Libsanitizer: committed upstream.
* Neon intrinsics: shared initial proposal of dejagnu-ization of my
existing tests.
* Branch
== Progress ==
* Disable-peeling: analyzed regression on one bench.
* Libsanitizer/aarch64:
- porting will require more effort than aarch32.
- some syscalls are not supported by aarch64
- libsanitizer expects frame to grow downwards (true on aarch32,
false on aarch64)
* PGO/LTO bug reported
== Progress ==
* Disable-peeling: looking at how to have less aggressive vectorization
* Libsanitizer/aarch64: initiated upstream discussion
* PGO/LTO bug reported by Doko: SD card too small to reproduce the problem
* Merges for linaro-gcc-2013.06: started looking at what to backport,
started
== Progress ==
* Merges for linaro-4.8-2013.06 and linaro-4.7-2013.06
- Spent most of my time on this activity, with Yvan
- A few cbuild issues, local disk full, and other local disk crash
- Investigating why the cross-validations lack libpthread and libdl
(required since libsanitizer
== Progress ==
* Merges for linaro-4.8-2013.06:
- investigated why the cross-validation lack libpthread and libdl.
- fixed cbuild to make these libs available in the same dir as ld-linux.so
- not sure why it wasn't necessary several weeks ago when I first
spawn libsanitizer tests: we changed
== Progress ==
* Completed list of backports from trunk to linaro-4.8 for 2013.07
release and sent it to Rob.
* Merged backport of address sanitizer in linaro-4.8 branch
* Aarch64 frame growing downward: checking what really needs to be
changed in GCC. Documentation not very verbose :-)
* Various
== Progress ==
* Short week (3 days off sick)
* Aarch64 frame growing downward: sent patch
* A few merges on Rob's behalf after approval by Yvan
* Prepared one more merge request
* Prepared for Connect
* Internal support
== Next ==
* Handle remaining backports for 4.8 release
* Disable peeling:
== Progress ==
* 2013.07 release preparation:
* remaining backports
* reverted 2 sets of patches from 2013.06
* started release process
* Worked on setting up an internal build + validation to monitor FSF
trunk on ARM
* Internal support
== Next ==
* All week at Connect
Hi,
On 11 July 2013 18:52, Christophe Lyon christophe.l...@linaro.org wrote:
Linaro GCC 4.8 2013.07 is the fourth release in the 4.8 series. Based
off the latest GCC 4.8.0+svn200355 release, it includes performance
improvements and bug fixes.
Interesting changes include:
* Updates to GCC
Hi,
Linaro is NOT an alternative to the Yocto project; we are
collaborating with them. For instance, there are recipes to build a
Yocto distribution using Linaro packages (e.g. the toolchain).
Regarding the support of armv5te, if you build your toolchain from the
sources we provide, the support
== Progress ==
* 2013-08 4.8 release:
- Reviewed merge requests sent by Yvan.
A few instabilities in x86/x86_64: re-spawned jobs came back clean.
Unexpected improvements in a9: actually the reference had
unexpected regression; re-spawned reference job came back clean.
- prepared
== Progress ==
* 2013.08 4.8 release:
-- merged many backports
- sorted a few dependencies problems between patches
- spawned all intermediate jobs (ie merge commits) to make sure
there was no regression
* 2013.08 4.7 release:
- made a trial branch merge to confirm that all builds succeed
== Progress ==
* 2013.08 4.8 release:
- completed achievable backports (postponed some with problems to
next release)
- created uploaded release. Will be announced next week along with 4.7
- Matthias a reported a problem in c++/java
* Aarch64 frame layout: submitted sample code for
== Progress ==
* Backports for 2013.09:
- updated list, assigned some to team members
- submitted several requests
- quite a few of them exposed dependencies, making it necessary to
make several attempts.
* Aarch64 frame layout: posted sample code using large frame on
gcc-patches to get
== Progress ==
* Backports for 2013.09:
- committed several
- reviewed
- submitted a few new ones
* Wiki pages cleanup
* GCC trunk cross-validation:
- need to work around results instabilities caused by incomplete
threads support in QEMU.
== Next ==
* Release 2013.09 next week after
The Linaro Toolchain Working Group is pleased to announce the release
of both Linaro GCC 4.8 and Linaro GCC 4.7.
Linaro GCC 4.8 2013.09 is the sixth release in the 4.8 series. Based
off the latest GCC 4.8.1+svn202157 release, it includes performance
improvements and bug fixes.
Interesting
== Progress ==
* AArch64 frame grows downward: no feedback yet.
* Disable-peeling: trying to tune the vectorizer cost model so that it
is less aggressive.
* AArch64 bootstrap failure: build it still on-going, so still hoping
to reproduce it.
* GCC trunk cross-validation:
- aarch64 added
-
== Progress ==
* AArch64 frame grows downward: no feedback yet.
* Disable-peeling: Vectorizer cost model has been changed upstream,
the current default now includes the effect of disabling peeling. I
have submitted benchmark jobs to check the exact effet; expecting some
regressions since the
The Linaro Toolchain Working Group is pleased to announce the
release of both Linaro GCC 4.8 and Linaro GCC 4.7.
Linaro GCC 4.7 2013.10 is the nineteenth release in the 4.7
series. Based off the latest GCC 4.7.4+svn203509 release, this is the
sixth release after entering maintenance.
Interesting
== Progress ==
* Releases 4.7 and 4.8 2013.10
* Tried cbuildv2: difficult because of our company proxy, making some
changes necessary to cbuildv2. Tutorial sessions in Connect will be
welcome.
* Started chasing a regression in armv5 targets, handed over to Kugan.
* Noticed regressions in some
Short week: 2 days off after Connect.
== Progress ==
* LP 1243656: reverted commit which causes a regression in GNU tar's tests.
* Committed Kugan and Zhenqiang's backports to our branch
* Status on backports: ILP32 support missing from binutils is blocking
quite a few GCC backports (because of
One day off
== Progress ==
* Prepared 4.7 and 4.8 2013.11 releases. Some delay because of board
crashes and disk full issues.
* Aarch64: committed 'frame grows downward' patch. This removes a
dependency for libsanitizer and libssp.
* libsanitizer on Aarch64: blocked by GCC trunk not bootstrapping
The Linaro Toolchain Working Group is pleased to announce the
release of both Linaro GCC 4.8 and Linaro GCC 4.7.
Linaro GCC 4.7 2013.11 is the twentieth release in the 4.7
series. Based off the latest GCC 4.7.4+svn204656 release, this is the
seventh release after entering maintenance.
Original Message
Subject:[Bug target/59216] [ARM] negdi*extendsidi regression
Date: Wed, 20 Nov 2013 18:06:14 +0100
From: christophe.lyon at st dot com gcc-bugzi...@gcc.gnu.org
To: Christophe LYON christophe.l...@st.com
http://gcc.gnu.org/bugzilla
== Progress ==
* Released GCC 4.7 and 4.8 2013.11 releases.
* Investigated potential regressions on trunk, as reported by
continuous cross-validation.
Reported some cases to Kyryll. Another, reported to Bin, turns out
to be an unrelated, unstable testcase recently introduced.
Will have to give
== Progress ==
* Disable peeling:
- spawned benchmarking jobs using recent trunk and another older
one to check for performance regressions.
- locally generated the code for the same benchmark to analyze the
differences
* cbuildv2:
- retried to create 4.8-2013.11 source release. Identified
== Progress ==
- cross-validation: (1/10). Follow-up, minor maintenance and
discussions on a few regressions. Now able to share top-level
reports.
- backports (1/10):
* multilib_defaults for 4.7
* committed all approved backport
* helped Michael solve some conflicts
- disable peeling:
== Progress ==
- 2013.12 releases (4/10):
* stalled due to lab unavailability.
* A couple of backports are waiting for approval, another one is
being debugged.
- cross-validation (4/10): fixed arneb+qemu validations.
- misc (2/10): misc conf-calls and meetings
== Next ==
- Make 2013.12
== Progress ==
- 2013.12 releases (4/10)
* Handover to Michael
* Committed remaining backports/branch merges
* Unexpected regression in 4.7 branch narrowed to a linker bug, now fixed.
- cross validations (2/10)
* stabilized armeb+qemu validations
- misc (4/10): misc conf-calls and
The Linaro Toolchain Working Group is pleased to announce the
release of both Linaro GCC 4.8 and Linaro GCC 4.7.
Linaro GCC 4.7 2013.12 is the twentiy first release in the 4.7
series. Based off the latest GCC 4.7.4+svn205768 release, this is the
eighth release after entering maintenance.
- 2013.12 releases (1/10)
* Sent announcements for 4.7 and 4.8 releases.
- 2014.01 releases (2/10)
* Created 4.7 and 4.8 branch merge requests (had handle some conflicts in 4.8)
* Looked at backporting the crypto intrinsics support into 4.8, but
there are dependencies with several other
- 2014.01 releases: (2/10)
* 4.7 ready, 4.8 needed a short daily to include our multilib patch
to support our binary releases.
* retried cbuildv2 and sent feedback. Should be mostly OK by now.
- cross-validations: (2/10)
* followup-up, bugzilla
* thinking about short term Neon intrinsics
The Linaro Toolchain Working Group is pleased to announce the
release of both Linaro GCC 4.7 and Linaro GCC 4.8.
As announced at Linaro Connect USA 2013 Linaro GCC is moving to a
pattern of quarterly stable releases, with engineering releases in the
intervening months. This is the first stable
== Progress ==
- releases (3/10)
* GCC 4.7 and 4.8 releases done
* more cbuild2 feedback
- cross-validations (2/10)
* followup
* adding capability to test a patch over a given revision on several
targets/cpu/fpu/runtestflags
- libsanitizer on AArch64 (3/10)
* most tests are now
* Libsanitizer for AArch64: (4/10)
- seems to be mostly working, but trouble with validation both using
the Foundation Model and qemu-aarch64.
- Some tests seems to loop forever while unwinding under qemu, but
run fine under the Foundation model
- Conversely the Foundation Model shows some
== Progress ==
* Libsanitzer for AArch64: (3/10)
- QEMU patch to handle missing mmap flag accepted.
- Charles was able to build GCC + run the sanitizer tests on board
- cleanup patch, ready to be sent to the LLVM list for approval
* Cross-validation: (1/10)
- extending timeout to 5h for
On 12 March 2014 09:57, Renato Golin renato.go...@linaro.org wrote:
On 11 March 2014 23:47, Felipe Rocha da Rosa frdar...@inf.ufrgs.br wrote:
I'm trying to build the native compiler to a arm a9 using this tutorial,
https://wiki.linaro.org/WorkingGroups/ToolChain/Using/GCCNative.
However, I
== Progress ==
* Back to work part-time (50%) for the next 3 weeks
* Easter Monday (1/5)
* (No Jira card - 2/5)
Analyzed at GCC trunk validations and reported some regressions.
The current commit rate is very high since stage1, and our compute
farm isn't fast enough. Should be OK after the
Very short week (3 half days)
== Progress ==
* GCC trunk cross-validation (2/10):
- monitored results, and reported some regressions/new fails
- moved away from Jenkins
- as commit rate has decreased, there is no backlog in validations
* Neon-intrinsics test (1/10):
- Continuing
Back full time
== Progress ==
* resumed 1:1 calls with Zhenqiang, Venkat, Charles.
* GCC trunk cross-validation (2/10):
- monitored results
- a few improvements/cleanups
* Neon-intrinsics tests (5/10)
- continuing conversion
- needs to add support AArch64 Neon overflow flag
* Misc
== Progress ==
* GCC trunk cross-validation (4/10)
- build broken last week-end, because of a
new optimization that broke glibc build.
- glibc fixed by Joseph mid-week, updated
- to help diagnose build failures earlier, I have setup
a reduced version of the validation framework,
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
Short week (2 days off) (4/10)
== Progress ==
* GCC trunk cross-validation (CARD-647) (2/10)
- reported 2 new compiler build failures and 2 regressions
- tested one proposed patch, which did not fix the regression
- trunk now builds OK again
* Neon intrinsics tests (1/10)
- cleaned
On 28 May 2014 21:52, João M. S. Silva joao.m.santos.si...@gmail.com wrote:
Hi,
I'm trying to follow
https://wiki.linaro.org/WorkingGroups/ToolChain/Using/GCCNative but it looks
like it is outdated? Can someone confirm?
After a quick glance, it looks valid.
E.g.:
configure: WARNING:
== Progress ==
* GCC trunk cross-validation (CARD-647) (6/10)
- recent LRA change to fix AArch64 compiler causes huge memory consumption.
- this has caused my validations to crash several servers, and I had
to stop them
until I could restart reliably.
- so far unable to restore them
-
Monday off. (2/10)
== Progress ==
* GCC trunk cross-validation (CARD-647) (3/10)
- improved scripts to avoid consuming to much memory
- improved kill signals handling when generating reports
- back to normal
- started looking at adding libstdc++ in the reports
- started looking at
On 17 June 2014 18:24, -- -- shining_diam...@mail.com wrote:
Hello,
I am trying to crosscompile on my laptop for Arm v7
I cannot understand how the linaro toolchain works. I do not see and .pdf
documentation
Can you please provide me with some documentation to start with?
Thank you
for this toolchain?
Thank you
Haris
Sent: Wednesday, June 18, 2014 at 5:08 PM
From: Christophe Lyon christophe.l...@linaro.org
To: -- -- shining_diam...@mail.com
Cc: Linaro Toolchain linaro-toolchain@lists.linaro.org
Subject: Re: Crosscompile for arm
On 17 June 2014 18:24, -- -- shining_diam
== Progress ==
* GCC trunk cross-validation (CARD-647) (5/10)
- fixes to email-driven robot, now generating html reports
- trouble shooting transcient problems with the compute farm
- added a57+crypto FPU configuration, still under test
- added libstdc++ reports
* AArch64 libsanitizer
builds/$TARGETS-linux/.config to meet your special requirement.
Sent: Tuesday, June 24, 2014 at 5:11 AM
From: Zhenqiang Chen zhenqiang.c...@linaro.org
To: -- -- shining_diam...@mail.com
Cc: Christophe Lyon christophe.l...@linaro.org, linaro-toolchain
linaro-toolchain@lists.linaro.org
== Progress ==
* GCC trunk cross-validation (CARD-647) (6/10)
- email robot is now working
- added list of ignored tests when reporting regressions, mainly
because they are unstable when run under qemu (threads...)
- a57+crypto FPU config looks OK
- tried to use contrib/test_summry to send
The Linaro Toolchain Working Group is pleased to announce the 2014.06
release of Linaro GCC 4.7.
As announced at Linaro Connect USA 2013 Linaro GCC moved to a pattern
of quarterly stable releases, with engineering releases in the
intervening months. This is the third stable release, and contains
I suggest you contact our support team:
https://support.linaro.org/home
Christophe.
On 1 July 2014 13:20, -- -- shining_diam...@mail.com wrote:
Dear Alexis,
thank you very much for the information below. However I stil do not
understand. Only by doing an untar of the tar file to the
== Progress ==
* Released gcc-linaro-4.7-2014.06 final (1/10)
* GCC trunk / 4.9 branch (2/10)
- reported regressions
- tested a preprocessor patch from Dodji (after his previous version
broke trunk build on ARM/AArch64*linux targets)
- fixed bugs in comparison script
* Neon intrinsics
== Progress ==
* GCC trunk cross-validation
- reported a few regressions
* Automation Framework (2/10)
- looked at Jenkins configuration logs of some failures
* AArch64 libsanitizer (1/10)
- tried to use cbuild2 in the lab to build test on HW, but all my
build attempts failed for various
== Progress ==
* GCC trunk/4.9 cross-validation (5/10)
- analysed reports sent during my holidays
- troubleshooting problems with the compute farm (semaphores
exhaustion, spurious parallel make failures, ...)
* 2014.09 release
- reviewed backport requests
* LCU14 preparation (slides)
== Progress ==
* GCC trunk/4.9 cross-validation (1/10)
- checking results
* bug #306 (bootstrap failure on i686) (3/10)
- fixed an incorrect backport than made GCC build to fail in stage1
- now trying to reproduce the original bug reported
* AArch64 libsanitizer (2/10)
- resumed work,
== Progress ==
* GCC trunk/4.9 cross-validation (1/10)
- monitoring results
- noticed failures on newly introduced tests when running on armeb.
Kyrill will fix his tests.
* bug #306 (bootstrap failure on i686) (1/10)
- unable to reproduce it
* AArch64 libsanitizer (3/10)
- asan and most
I fixed a problem in the i686 build recently, but the symptom was
different from your: GCC itself failed to build.
Maybe it's worthing try 09 release (which will probably be announced today)
Christophe.
On 11 September 2014 11:22, Bernhard Rosenkränzer
bernhard.rosenkran...@linaro.org wrote:
== Progress ==
* GCC trunk/4.9 cross-validation (2/10)
- noticed a couple of newly introduced failing tests in some corner cases
- improved notification of selected commits to help fill the
backports speadsheet
* AArch64 libsanitizer
- answered Marcus/Andrew after their feedback
* Misc
Hello Joel
Could you provide us with:
- the exact command line used (the one calling GCC, with all the flags)
- the output of gcc -v the see how it was configured
From what you say it looks like your compiler is currently configured
to generated hard-float code by default, and that you are
Short week, 2 days holiday (4/10)
== Progress ==
* GCC trunk/4.9 cross-validation (2/10)
- reported a few new FAILs
- trying to allocate time to fix new FAILs introduced in the 4.9
branch on devirt-28a.C, mostly because a testsuite configuration
problem.
- fixed reporting of email-driven
== Progres ==
* GCC trunk/4.9 cross-validation (CARD-647) (3/10)
- aarch64 address sanitizer tests currently all fail at execution
under qemu because they try to reserve 50GB of memory. Tried to push
the limits with no success so far.
- working on fixing support for testcases generating a
== Progress ==
* GCC trunk/4.9 cross-validation (CARD-647) (2/10)
- trunk build for aarch64 reported to fail because libsanitizer
requires an update. Pinged libsanitizers maintainers but got no answer
so far.
- posted testsuite patch to test if -shared is supported
- managed to find how to
On 23 October 2014 12:00, Will Newton will.new...@linaro.org wrote:
On 23 October 2014 10:44, Yvan Roux yvan.r...@linaro.org wrote:
Hi,
after the recent lkml thread on blacklisting some GCC versions (see
below) and the issue in identifying accurately our releases, I propose
to add some
Short week, 2 days off
== Progress ==
* GCC trunk/4.9 cross-validation (2/10)
- committed testsuite patch to support forcing -mword-relocations
option when compiling testglue.c
* Neon intrinsics tests (2/10)
- committed the 1st batch (21 commits)
* AArch64 sanitizer
- libsanitizer
== Progress ==
* GCC trunk/4.9 cross-validation (1/10)
- monitoring
- tracking cause of spurious interrupted system call
- testing small changes in harness
* AArch64 sanitizers (2/10)
- resumed discussion with Maxim/Arnd, the situation is clearer now
- started looking at running asan
== Progress ==
* GCC trunk/4.9 monitoring (2/10)
- still tracking cause of random interrupted system call errors
- checked possible regressions
* AArch64 sanitizers (1/10)
- managed to build on board, didn't try to run the tests yet
* Neon intrinsics tests (2/10)
- fixed a couple of bugs
Hi all,
I've asked ITS to install a git post-commit hook to send an email
after commits in the toolchain git repos.
It turns out that they prefer to send such email to mailing-lists, to
avoid having to maintain the list of recipients themselves, which of
course really makes sense.
So far, we
== Progress ==
* GCC trunk/4.9 monitoring (1/10)
- still tracking cause of random interrupted system call errors
- flagged a few wrong new Neon testcases
* AArch64 sanitizers (1/10)
- documented build process (based on configure) works on aarch64,
but still unable to run the sanitizer tests
== Progress ==
* 2015.01 release
- reviewed Yvan's backports
* GCC trunk/4.9 monitoring (2/10)
- still tracking cause of random interrupted system call errors
* AArch64 sanitizers (1/10)
- LLVM+compiler-rt build seems OK, but still unable to run the tests on Juno
* Neon intrinsics tests
1 - 100 of 407 matches
Mail list logo
