similar to: Vanderpool Preliminary Specification for IA-32 and Intel Itanium Processors

Displaying 20 results from an estimated 4000 matches similar to: "Vanderpool Preliminary Specification for IA-32 and Intel Itanium Processors"

2005 Dec 10
1
Intel VT (Vanderpool) hardware
Xen 3.0 is supposed to support Intel VT (Vanderpool) hardware. I can not find any place that has these Intel CPUs or systems. Anyone know where to get Intel VT (Vanderpool) CPUs or systems? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________
2009 Jul 17
2
[LLVMdev] Removal of IA-64 target
On Jul 16, 2009, at 9:49 PM, Marcel Moolenaar wrote: >> For us to keep IA64 around (and for it to be minimally useful for >> your >> work!), I think that the backend should pass most of the simple >> programs in MultiSource/Benchmarks for example. It does *not* need >> to >> produce amazingly fast code, but the code needs to work. I don't >>
2009 Jul 17
0
[LLVMdev] Removal of IA-64 target
On Jul 16, 2009, at 10:22 PM, Chris Lattner wrote: > >> However, I do not want to go anywhere near trying to achieve optimal >> code generation right now. Getting functional completeness is as high >> as I dare to shoot. I presume that it'll be daunting enough. > > It depends a lot on your background, but yes it is a substantial > amount of work. Low-level
2005 Aug 09
3
Build on Itanium fails
Hi Guys, I hope this is the correct mailing list for this question. I have a dual 1.6 Ghz Itanium with 4 Gb of memory. Yes, a lot of power for Asterisk. I am running SuSE Enterprise Server with the 2.6.5-7.97-default kernel. I have just started to look into Asterisk and I am in the building stage. Now building something on Itanium is almost always a bit of a challange. This is unfortunately
2002 Oct 15
1
PxeLinux and Itanium
Your PxeLinux is really a good product and contains really good features (i.e memdisk). But PxeLinux is a very low level program, contains assembly code and seems to no be portable to Itanium architectures. Does a version of PxeLinux planned for Itanium architecture ? PS:On my configuration, option pxelinux.reboottime (code 211) you give in your documentation removes my "default router"
2009 Jul 17
0
[LLVMdev] Removal of IA-64 target
On Jul 16, 2009, at 5:51 PM, Chris Lattner wrote: > > On Jul 16, 2009, at 2:30 PM, Marcel Moolenaar wrote: > >> >> BTW: I don't run Linux at all, so no Linux/ia64 support. >> I can see how that could be a problem for people. >> >> Anyway: my case is a weak one and I would understand if the >> target get axed without considering my email/request...
2008 Jan 10
0
[LLVMdev] LLVM Build Problems on Itanium
Hi, I am having some difficulties building llvm on Itanium. My procedure for building LLVM is: cd /liberty/llvm.ia64/llvm-2.1 ./configure make ENABLE_OPTIZED=1 cd /liberty/llvm.ia64/obj /liberty/llvm.ia64/llvm-gcc4.2-2.1.source/configure --prefix=/liberty/llvm.ia64/install --enable-llvm=/liberty/llvm.ia64/llvm-2.1/ --enable-languages=c,c++ --disable-shared The build of llvm seems to
2003 Feb 03
2
itanium
I am trying to compile R-1.6.1 on an itanium. using either gcc 2.96 or gcc 3.0.4 nad either the supplied Redhat blas libs or the supplied code (ie wiht the --no-blas option) I get this error. Has anyone who has compiled R for the itanium advise me on the compilers versions and flags that they used? thanks bye rob gcc -shared -L/usr/local/lib -o lapack.so Lapack.lo
2016 May 05
4
RFC: Adding an itanium c++ demangler to lib/Support
We are trying out lld ELF on windows. It works great, but a big difference from running it on linux is that it cannot demangle c++ names since there is no itanium demangler available on windows. We have an implementation in libcxxabi/src/cxa_demangle.cpp. I see that there was some discussion about having a version of that in lib/Support, but I don't think a patch was ever posted. So, some
2009 Jul 17
2
[LLVMdev] Removal of IA-64 target
On Jul 16, 2009, at 2:30 PM, Marcel Moolenaar wrote: > > BTW: I don't run Linux at all, so no Linux/ia64 support. > I can see how that could be a problem for people. > > Anyway: my case is a weak one and I would understand if the > target get axed without considering my email/request... Hi Marcel, There are two levels of problems with the IA64 backend. On the first
2006 Feb 01
0
Itanium 64 Bit Support?!
Does anyone know if Xen is currently supporting Itanium on 64 Bit!? Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com <mailto:diederit@ing.boehringer-Ingelheim.com> * Phone: +49 (0)6132/77-98151
2008 Jun 09
1
Clustersuite package installation failed in Itanium server
Dear All, I am new in Itanium server Installation and I have installed all the CentOS4.4 ia64 CDs and I have try to install clustersuite packages and i am getting the following error messages like error: %post(package name here) scriptlet failed, exit status 255 and error: %pre(package name here) scriptlet failed, exit status 255 problem Cluster Suite RPMS are ccs-1.0.7-0.i686.rpm
2008 Jan 10
2
[LLVMdev] LLVM Build Problems on Itanium
On Jan 10, 2008, at 12:52 PM, Thomas Jablin wrote: >> > Based on your response I've removed the #undef DBX_DEBUGGING_INFO in > gcc/config/ia64/sysv4.h. I don't need stabs debugging so if it is > broken > in my final build, I won't care. After doing so, my llvm-gcc build > runs > for a much longer time before finally dying while running xgcc. Here > is
2008 Jan 10
0
[LLVMdev] LLVM Build Problems on Itanium
Hi, I've figured out a little more. #if defined DBX_DEBUGGING_INFO || XCOFF_DEBUGGING_INFO guards the declaration of type_queue, however, neither is defined on Intanium. In gt-dbxout.h type_queue's uses are unguarded and thus are undefined on Itanium. When I compared llvm-gcc's gt-dbxout.h with FSF gcc's, I found that type_queue was never used in FSF gcc's version. Does
2004 Jun 10
1
Failure to compile on Itanium
I am trying to compile R on an Itanium machine running Red Hat 7.2 and gcc version 2.96. The build fails with the following symptoms: g77 -fPIC -g -O2 -c cmplx.f -o cmplx.lo g77 -fPIC -g -O2 -c cmplxblas.f -o cmplxblas.lo gcc -shared -L/usr/local/lib -o libRlapack.so dlapack0.lo dlapack1.lo dlapack2.lo dlapack3.lo cmplx.lo cmplxblas.lo -L/usr/local/lib
2003 Apr 21
1
R on HP/HPUX IA-64
Does the current version of R run on HP/HPUX IA-64 Itanium processors?
2008 Jan 10
0
[LLVMdev] LLVM Build Problems on Itanium
Devang Patel wrote: > On Jan 10, 2008, at 10:29 AM, Thomas Jablin wrote: > > >> Hi, >> >> I've figured out a little more. #if defined DBX_DEBUGGING_INFO || >> XCOFF_DEBUGGING_INFO guards the declaration of type_queue, however, >> neither is defined on Intanium. In gt-dbxout.h type_queue's uses are >> unguarded and thus are undefined on
2005 Dec 12
3
OS/2 and eComStation
Hi, Hoping someone can help me with some question on Xen 3.x and Intel VT (Vanderpool) hardware. Can IBM OS/2 or Serenity Systems eComStation now be run with Xen and Intel Vanderpool enabled CPUs? If not, what is needed? Are any drivers needed? Do you know of anyone working on getting Xen to support OS/2 or eComStation? > Jan 21,2004, Mark A. Williamson wrote: > Afraid so. > With
2017 Jun 22
3
RFC: Cleaning up the Itanium demangler
On June 22, 2017 at 5:51:39 AM, Pavel Labath (labath at google.com) wrote: I don't have any concrete feedback, but: - +1 for removing the "FastDemagler" - If you already construct an AST as a part of your demangling process, would it be possible to export that AST for external consumption somehow? Right now in lldb we sometimes need to parse the demangled name (to get the
2017 Jun 22
3
RFC: Cleaning up the Itanium demangler
On 6/21/17 5:42 PM, Rui Ueyama wrote: > I'm very interested in your work because I've just started writing a > demangler for the Microsoft mangling scheme. What I found in the > current Itanium demangler is the same as you -- it looks like it > allocates too much memory during parsing and concatenates std::strings > too often. I could see there's a (probably big)