similar to: Para-virtualized linux kernel release for the Tegra2 harmony board.

Samsung Enterprise Portal mySingle Hi, I am happy to announce that a patch for a new emulator platform Goldfish (QEMU 0.82 based Android emulator) is released at wiki.xensource.com/xenwiki/XenARM. Sang-bum _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Just noticed that in the support section of the Harmony Remotes, you can now download version 7.7.0 instead of the earlier 7.6.0. No visible changes for the Harmony One wrt functionality. Still only 24 favorites for TV channels, still no favorites for listening to the radio. Did anybody else noticed some changes ?

Hi all, Please check out our recent ISCA publication that introduces a new performance profiling technique for analyzing parallel programs along with an open source tool to collect the profiles. The tool is written into LLVM's LTO. Could someone please add the paper to http://llvm.org/pubs/ ? Here is the citation: Harmony: Collection and Analysis of Parallel Block

My first ARM testing results or lack of them indicate that 3.0 release requires some some beefy machines to build. It is not so much raw cpu speed but memory and lots of it. My builds got to linking llc and at that point linker started eating megabytes of memory like chocolate. So sadly chumbys, beagleboards, iThingis(?), Raspberry Pis, Gumstix and even inexpensive Tegra2 boards seem to be out of

On 10/17/2011 09:20 AM, Pawel Wodnicki wrote: > > My first ARM testing results or lack of them indicate > that 3.0 release requires some some beefy machines to build. > It is not so much raw cpu speed but memory and lots of it. > My builds got to linking llc and at that point linker started > eating megabytes of memory like chocolate. > > So sadly chumbys, beagleboards,

Also, was this with binutils-gold? -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Tobias Grosser Sent: 17 October 2011 09:56 To: Pawel Wodnicki Cc: llvmdev Subject: Re: [LLVMdev] LLC ARM Backend maintainer On 10/17/2011 09:20 AM, Pawel Wodnicki wrote: > > My first ARM testing results or lack of them indicate > that

On 3/27/11 4:38 AM, Bill Wendling wrote: > Hi all, > Please check out sources. Compile things. Report bugs. Etc. I'm not sure if this is useful as is, but attached is output of `make check` for llvm+clang, on a Tegra2 machine with ubuntu linux. The ocaml binding failures are due to the fact there is no ocamlopt on arm, even though there is ocaml/ocamlc, and the bindings compile

Evan, > I'm the code owner of LLVM codegen and targets. I'm also the one of main developers on the original ARM target. That means, I would make the decisions on major development on ARM target if there are decisions to be made. > > But my role is very different from what people are looking for in this thread. To properly qualify a target like ARM which are supported on many

arm: implement exception and hypercall entries. xen/arch/arm/xen/Makefile | 3 + xen/arch/arm/xen/asm-offsets.c | 61 ++++++++ xen/arch/arm/xen/entry.S | 596 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ xen/arch/arm/xen/hypercalls.S | 67 +++++++++ xen/arch/arm/xen/physdev.c | 41 +++++ 5 files changed, 768 insertions(+), 0

Hi all, The good news: RC2 testing was successful in that it uncovered a bad regression from 2.8 (which existed in top-of-tree). It also showed that there was an unincorporated fix that needed to go into the clang branch. The bad news: I'm truncating the RC2 testing phase and announcing the RC3 testing phase. Hopefully, because we caught the bugs in time this phase won't impact the

On 3 January 2013 22:09, Nadav Rotem <nrotem at apple.com> wrote: > The loop vectorizer is now enabled by default. > I thought that was just a temporary arrangement to get the feel for it, not to actually have it on all the time (next release). Is it just for -O3 or lower too? This can cause problems, for instance on ARMv7, the default is that NEON is present, but Tegra2 doesn't

Hi all, I recently used smbtar (Samba Version 2.0.4) to create a tar file "backup" of an NT filesystem. However, when using GNU tar to extract the tar file, I get a little ways into the 'tar xvpf ../file.tar' command and get a whole bunch of errors: tar: Read error on ../file.tar: Invalid argument tar: Read error on ../file.tar: Invalid argument tar: Read error on

Hi, I've seen a problem where on recovery after a crash the orphan cleanup code clears the read_only bit and does not reset it. This causes the the fsck to drop to the "fix filesystem" prompt simply because the root filesystem is now mounted rw. It looks like this: Creating rootdevice Mounting rootfilesystem EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs:

Hi, I''m trying to boot XEN via network, so I''m trying to create a rootfilesystem over a RAM disk for XEN. Has anyone done that before? Thanks, Gianluca _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

All, I am playing with virtualization on centos 5. I took my old redhat 7 disks and created a 10GIG virtual disk, I installed redhat 7. Now I am trying to get the EXACT image copied off of my actual redhat 7 disk so that I know it is the same (including all patches, updates and OTHER things I did to it that I have forgotten about). I booted the redhat 7 image just fine at this point. I also

arm: implement ARMv7 tlb ops. xen/arch/arm/xen/Makefile | 1 + xen/arch/arm/xen/cache-v7.S | 17 +++++------------ xen/arch/arm/xen/domain_build.c | 6 +++--- xen/arch/arm/xen/tlb-v7.S | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 60 insertions(+), 15 deletions(-) Signed-off-by: Jaemin Ryu <jm77.ryu@samsung.com> diff -r c6a412adfae7

On 27 May 2011 19:47, Jim Grosbach <grosbach at apple.com> wrote: > Not exactly. The distinction is clear, it's just not expressed as an > either/or question. Specifically, the code generator considers NEON to be a > proper superset of VFP3. So if it has only VFP3, that's all it will use. If > it has NEON, it assumes it also has VFP3 and can use either. Indeed. >

On 3 January 2013 21:53, Nadav Rotem <nrotem at apple.com> wrote: > > I am asking this because I would like to have loop vectorization > disabled for targets that don't support SIMD instructions (for example, > standard mips32). > > Loop vectorization bloats the code size and prolongs compilation time > without any improvement to performance for such targets. >

On Jan 3, 2013, at 2:05 PM, Renato Golin <renato.golin at linaro.org> wrote: > Isn't the vectorizer disabled by default? The loop vectorizer is now enabled by default. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130103/4645b2e8/attachment.html>