search for: cpu_type

Hi Bob! I could not find llvm file for ARM target in llvm-gcc 4.2 front end source code. $llvm-gcc-src/gcc/config.gcc file alpha*-*-*) cpu_type=alpha need_64bit_hwint=yes # LLVM LOCAL begin out_cxx_file=alpha/llvm-alpha.cpp # LLVM LOCAL end ;; ... arm*-*-*) cpu_type=arm extra_headers="mmintrin.h" ;; ... i[34567]86-*-*) cpu_type=i386 # LLVM LOCAL begin out_cxx_file=i386/llvm-i386.cpp # LLVM LOCAL end # APPLE LOCA...

...t there are some ARM-related changes to config.gcc in llvm-gcc. On Sep 30, 2009, at 9:44 AM, Jin Gu Kang wrote: > Hi Bob! > > I could not find llvm file for ARM target in llvm-gcc 4.2 front end > source code. > > $llvm-gcc-src/gcc/config.gcc file > > alpha*-*-*) > cpu_type=alpha > need_64bit_hwint=yes > # LLVM LOCAL begin > out_cxx_file=alpha/llvm-alpha.cpp > # LLVM LOCAL end > ;; > ... > arm*-*-*) > cpu_type=arm > extra_headers="mmintrin.h" > ;; > ... > i[34567]86-*-*) > cpu_type=i386 > # LLVM LOCAL b...

....git) Dom0 My platform is Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz My problems are: In Dom0, But hardware performance counters don''t be mounted after initialization (opcontrol --init) # ls /dev/oprofile backtrace_depth cpu_buffer_size pointer_size buffer cpu_type stats buffer_size dump time_slice buffer_watershed enable 0(and 1,2,3) directories are not exist. Is there any reason for this ? Any help is appreciated. Thanks, Yuto Nakai _______________________________________________ Xen-users mailing list Xen-user...

....git) Dom0 My platform is Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz My problems are: In Dom0, But hardware performance counters don''t be mounted after initialization (opcontrol --init) # ls /dev/oprofile backtrace_depth cpu_buffer_size pointer_size buffer cpu_type stats buffer_size dump time_slice buffer_watershed enable 0(and 1,2,3) directories are not exist. Is there any reason for this ? Any help is appreciated. Thanks, Yuto Nakai _______________________________________________ Xen-users mailing list Xen-user...

my system configuration xen 3.4.2, oprofile 0.9.5( xenoprof patched ), dom0( jeremy''s pvops kernel 2.6.31.6 - patched dullor''s xenoprof patch ), domU( vanilla kernel 2.6.32 with paravirt enabled ), distribution( ubuntu 9.10 ) In passive mode, xenoprof seems to work well, opreport showed good information. but, in active mode, it seems not to be done correctly. my command is

Is possible to install Centos 5 on a 586 CPU? (cpu_type = 5) Thanks a lot.

Unlike llvm itself, llvm-gcc needs to be configured for a particular target architecture. It looks like you're using a copy of llvm-gcc that was built to generate x86 code. On Sep 30, 2009, at 6:27 AM, Jin Gu Kang wrote: > Dear LLVM members. > > I am compiling coreutils-7.4 package for ARM linux using LLVM 2.5 > version. > > When i compiled 'od' program in

I am trying to set up a flexible infrastructure for the assembly code. Basically what I want is configure.in determination of basic machine type (intel/compatible, alpha, ppc), then within that (say intel) the code will detect variants like MMX, SSE, and use the right routines. I know how to do the second, but what is a good way to do the first? Linux/Cygwin/Solaris seem to support the MACHTYPE

Dear LLVM members. I am compiling coreutils-7.4 package for ARM linux using LLVM 2.5 version. When i compiled 'od' program in coreutils package using LLVM 2.5, i could see the error message on llc processing. > llvm-gcc -emit-llvm ./od.c -c -o ./od.bc -other-options... > llc -march=arm ./od.bc -f -o ./od.s llc:

...-m variants that mean intel 386 compatible? > (i386, i586, i686, athlon? etc). The best way to do this is to let autoconf work its magic for you. Use AC_CANONICAL_TARGET in configure.in, and it will place canonical system type for the target in the shell variable 'target' in the form CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM. Be sure to use the target, not the host, to allow cross-compiling. It will also be broken out into target_cpu, target_vendor and target_os. So you can use $target_cpu for your tests. A simple: case $target_cpu in i*86) blahblah ;; powerpc) blahblah ;;...

...# distribute this file as part of a program that contains a -# configuration script generated by Autoconf, you may include it under -# the same distribution terms that you use for the rest of that program. -# -# The first argument passed to this file is the canonical host specification, -# CPU_TYPE-MANUFACTURER-OPERATING_SYSTEM -# or -# CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM -# The environment variables CC, GCC, LDFLAGS, LD, with_gnu_ld -# should be set by the caller. -# -# The set of defined variables is at the end of this script. - -# Known limitations: -# - On IRIX 6.5 with CC=&q...

Patch 1 removes CONFIG_SMP Patch 2 removes separate smp_{,r,w}mb()s as a result of patch 1 Patch 4 removes __ia64__ defines from the x86 arch tree Patch 3 is related to patch 4 and changes the VIOAPIC to emulate version 0x20 as a performance gain. It preceeds Patch 4 so as to be more clear about the functional change. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>

Hello, would it be possible to update config.sub and config.guess to the latest versions (or at least version from automake-1.13.1) in order to support new architectures based on the ARM 64 bit CPU? Patch: http://plautrba.fedorapeople.org/openssh/openssh-latest-config.sub-config.guess.patch Related Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=926284 Thanks, Petr

I am rebasing Fedora rawhide oprofile package to oprofile-0.9.7. The xenoprof patches on http://xenoprof.sourceforge.net/#download look a bit dated. The newest version is for oprofile-0.9.5. I massaged the patch oprofile-0.9.5-xen.patch to apply to oprofile-.0.9.7. Attached is that updated patch. Does this look reasonable? Is there a desire to get this into upstream oprofile? Or should the

Renato, When I tried running "opcontrol --start" (after previously running "opcontrol --start-daemon") in dom0, I get this error message: /usr/local/bin/opcontrol: line 1639: echo: write error: Operation not permitted and this message in the Xen console: (XEN) xenoprof: operation 9 failed for dom 0 (status : -1) It looks like opcontrol is trying to do this: echo 1 >

Renato, When I tried running "opcontrol --start" (after previously running "opcontrol --start-daemon") in dom0, I get this error message: /usr/local/bin/opcontrol: line 1639: echo: write error: Operation not permitted and this message in the Xen console: (XEN) xenoprof: operation 9 failed for dom 0 (status : -1) It looks like opcontrol is trying to do this: echo 1 >

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of