[ACTIVITY] report week 7

2013-02-15 Thread Peter Maydell
Progress:
 * rebased qemu-linaro and sorted out with Serge what he requires
   in the way of patches for Ubuntu's upcoming code freeze. I plan
   to set up and test the 2013.03 release a week or two early both
   so that there is a patchset ready for the Ubuntu freeze and also
   to avoid clashing with Connect week.
 * some patches to clean up QEMU's logging functions so they can
   be used more widely in place of ad-hoc printf
 * cleanup patchset to get rid of sysbus_add_memory() function
 * LP:1079080 -- fixed serious bug in QEMU's Thumb-mode srs insn
 * upstream discussion about what to do about QEMU's disassembler
   license-clash issues:
http://lists.gnu.org/archive/html/qemu-devel/2013-02/msg02122.html

 * NB: I now work a 4 day week, excluding Wednesdays

-- PMM

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


[ACTIVITY] 11 - 15 Feb

2013-02-15 Thread Renato Golin
== Progress ==

* Vectorizer
 - Progressing on the global structure alias analysis (discussions, drafts,
failed attempts)
 - Interesting Linpack results for vectorizer, investigating performance
 - http://www.systemcall.org/blog/2013/02/llvm-vectorizer/
 - http://llvm.org/bugs/show_bug.cgi?id=15247

* Buildbots
 - Took Chromebook out, since Pandas are fast enough
 - Creating LNT test-suite buildbot
 - http://llvm.org/viewvc/llvm-project?view=revision&revision=175081
 - http://lab.llvm.org:8011/builders/clang-native-arm-lnt
 - Still a few rounds until it works properly

* Distributed Builds
 - Distributed compilation works somewhat on Pandas
 -
http://www.systemcall.org/blog/2013/02/distributed-compilation-on-a-pandaboard-cluster/
 - It's better, cheaper and easier to use Chromebooks / Arndales, though...

* LAVA
 - Tracking LLVM git repo in git.linaro.org
 - Trying to build from that repo, LAVA doesn't like it... :/

* EuroLLVM
 - We're not sponsoring it any more, will still help organize

== Plan ==

* Continue Global Alias Analysis, I seem to be getting close to something
worth sending (and learning a lot in the process)
* Make sure LNT buildbot is up and running with vectorizer (O3)
* Check with Dave Piggot why git.linaro doesn't work with LAVA
* Inspect why some (loop+bb) vectorized results are poor on ARM
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: Hard Floating Point Question

2013-02-15 Thread Fernan


>Christophe Lyon  writes:

> 
> Regarding your problems with ffmpeg, I'm sorry that I don't know how
> cmake works, but after spending some time trying to understand why
> cross-building fails, here are my remarks:
> 
> - installing packages such as libavcodec-dev installs the version for
> your host, not for your ARM target

Hi Christophe,

thanks for replay.

ok I will take it into account.

> - 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 

> - on my system, I have noticed that cmake says 'Could NOT find JPEG),
> then "Media I/O: JPEG: libjpeg (ver 62)" and I can see that g++ is
> called with -I/3rdparty/libjpeg, which is confusing

Same thing happens to me with FFMPEG

> - similarly, it looks like cmake is calling pkg-config which most
> probably queries the host, not the target FS
> - you have to make sure that the build process will find or build all
> the dependencies for ARM, which probably means it has to build ffmpeg
> - I don't know if all these are peculiarities of cmake or OpenCV, but
> it makes me wonder whether OpenCV is really supporting
> cross-compilation?
> - did you ask OpenCV community?

I could see OpenCV community recomend other ways to do what I want.

> 
> Sorry to ask more questions 
:)
> 
> Christophe.

Best regards.



___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: Hard Floating Point Question

2013-02-15 Thread Zhenqiang Chen
On 4 February 2013 02:08, Matthew Gretton-Dann
 wrote:
> On 2 February 2013 00:13, Derek Rollend  wrote:
>> Hello,
>>
>> I am currently trying to determine how much I can optimize OpenCV using the
>> ARM's VFP and the Linaro nano image.  I have downloaded the
>> arm-linux-gnueabihf-gcc & arm-linux-gnueabihf-g++ compilers, successfully
>> cross-compiled OpenCV using those compilers (with -O3 -mfloat-abi=hard
>> -ftree-vectorize -funroll-loops), and compiled an example OpenCV program
>> with the arm-linux-gnueabihf-g++ compiler (with the same flags).  However,
>> when I try and run my executable within Linaro (running on a gumstix overo)
>> I get "/lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.15' not found
>> (required by /usr/lib/libopencv_core.so.2.2).
>>
>> I assume that this is because on my build machine (x86 Ubuntu 10.04) where I
>> cross compiled the OpenCV libraries I am using libc-2.15, and on the target
>> (gumstix) the loader can't find libc-2.15.  However, within the
>> gcc-linaro-arm-linux-gnueabihf-4.7 tar ball I downloaded today, there is a
>> libc-2.15.so file in there that I copied into /lib/ on the gumstix.  Still
>> no success though when I try running my executable.
>>
>> Any recommendations on things to try?  I am hesitant to just put a newer
>> version of glibc in Linaro as it seems like that could screw a lot of things
>> up.  Should I attempt to re-build OpenCV somehow with an older version of
>> glibc (namely libc-2.13)?
>
> Expand the entire sysroot tarball you have onto your ARM board into
> some location (say /opt/gcc-linaro - but anywhere will do).  Then do:
> LD_LIBRARY_PATH=/opt/gcc-linaro/lib/arm-linux-gnueabihf program-to-execute 
> args


Please try to use --sysroot option.
copy the entire sysroot directories (/lib, /usr/lib, /usr/include) you
have onto your ARM board into some location (say /opt/gcc-linaro) on
your host machine and keep the dir layout, i.e. After copy, you will
have:

/opt/gcc-linaro/lib/...
/opt/gcc-linaro/usr/lib/...
/opt/gcc-linaro/usr/inlcude...

Then compile your project with additional gcc option: --sysroot=/opt/gcc-linaro/

-Zhenqiang

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


[ACTIVITY] 11 - 15 Feb

2013-02-15 Thread Kugan Vivekanandarajah
== Progress ==
-Spawned CBUILD tasks with and without the patch proposed by Chung-Lin
Tang to test current status of "Fix EPILOGUE_USES regression in
CoreMark". Job is still in the queue.
-Read references listed in gcc/ira.c to understand gcc IRA and went
through the source code.
-Experimented with simple test cases to analyse IRA debug output.


== Plan for next week ==
- Analyse CoreMark results if ready and work on improvements.
- Start with research for Removing unnecessary zero/sign extends when
not working on "Fix EPILOGUE_USES regression in CoreMark.

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain