Displaying 8 results from an estimated 8 matches for "__sparcv9".
2004 Oct 07
2
[LLVMdev] problem with lli (llvm 1.3)
Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9" but
there was no output. Maybe this is the probelm, I do have
CXX = g++ -mcpu=v9
CC := gcc -mcpu=v9
in the Makefile.config. Do I need to add -m64 as well? Thanks.
Shukang
On Thu, 7 Oct 2004, Misha Brukman wrote:
> Is your compiler configured to define __sparcv9 when it compiles?
>...
2004 Oct 07
0
[LLVMdev] problem with lli (llvm 1.3)
On Thu, Oct 07, 2004 at 06:46:18PM -0400, Shukang Zhou wrote:
> Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9"
> but there was no output. Maybe this is the probelm, I do have
>
> CXX = g++ -mcpu=v9
> CC := gcc -mcpu=v9
>
> in the Makefile.config. Do I need to add -m64 as well? Thanks.
Just run the test that I mentioned before:
> On Thu, 7 Oct 2004, Misha Brukman wrote:
> &...
2001 Jun 29
1
wtmpx problem on Solaris 8 sparcv9 (64bit) environment
...h-2.9p2.cast/loginrec.c
--- openssh-2.9p2.org/loginrec.c Wed May 9 05:34:33 2001
+++ openssh-2.9p2.cast/loginrec.c Thu Jun 28 11:06:22 2001
@@ -887,7 +891,11 @@
/* write a utmpx entry with the system's help (pututxline() and pals) */
# ifdef UTMPX_USE_LIBRARY
static int
+#ifdef __sparcv9
+utmpx_write_library(struct logininfo *li, struct utmpx *utx)
+#else
utmpx_write_library(struct logininfo *li, struct utmpx *utx)
+#endif
{
setutxent();
pututxline(utx);
@@ -902,7 +910,11 @@
/* write a utmp entry direct to the file */
static int
+#ifdef __sparcv9
+utmpx_write_d...
2004 Oct 07
0
[LLVMdev] problem with lli (llvm 1.3)
...tecode using interpretation ("lli -force-interpreter=true
> test.bc), it works fine. But if I use the JIT compiler ("lli
> -force-interpreter=false test.bc"), I got a Segmentation Fault error,
> even for a small program like helloworld.
Is your compiler configured to define __sparcv9 when it compiles?
The following should tell you:
% touch /tmp/file.c
% gcc -dM -E /tmp/file.c | grep __sparcv9
If the output is similar to the below, you're fine:
#define __sparcv9 1
If the above command gives no output, then you need to specify -mcpu=v9
or reconfigure/recompile GCC to defau...
2004 Oct 07
1
[LLVMdev] problem with lli (llvm 1.3)
I'm sorry, I did not completely understand your email, let me clarify my
response.
On Thu, Oct 07, 2004 at 06:46:18PM -0400, Shukang Zhou wrote:
> Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9"
> but there was no output. Maybe this is the probelm, I do have
>
> CXX = g++ -mcpu=v9
> CC := gcc -mcpu=v9
>
> in the Makefile.config. Do I need to add -m64 as well? Thanks.
Just run the test that I mentioned before:
> On Thu, 7 Oct 2004, Misha Brukman wrote:
> &...
2004 Oct 07
2
[LLVMdev] problem with lli (llvm 1.3)
Hi,
I am working with llvm 1.3 on a sparcv9 machine. I have successfully built
llvm and llvm-gcc frontend. I can run many tools including llvmgcc,
llvm-dis, and llc. After using /opt/SUNWspro/bin/cc to assemble .s file
into a program binary, I can run the binary correctly as well.
I am interested in the JIT compiler (lli). When I directly run the
LLVM bytecode using interpretation ("lli
2004 Oct 10
2
[LLVMdev] building LLVM (question about ELF class)
...ELFCLASS64
ld: fatal: File processing errors. No output written to
/a/athena/uf24/zhou/rese
arch/llvm/src/lib/Debug/.libs/libprofile_rt.so.0.0.0
collect2: ld returned 1 exit status
-----------
I have installed the llvm-gcc frontend before I configured and built LLVM.
I have tested that I have got __sparcv9 #defined, by "gcc -mcpu=v9 -m64
-dM -E hello.cpp | grep __sparcv9".
I have also added "/usr/cs/lib/sparcv9" to the beginning of
$LD_LIBRARY_PATH to force dynamic linking with 64-bit libraries at
run-time; otherwise 32-bit libraryies will be used, which will cause an
error that...
2020 Feb 09
2
[RFC PATCH] Add SHA1 support
...BLOCK;
+ HASH_BLOCK_DATA_ORDER(c, p, 1);
+ c->num = 0;
+ memset(p, 0, HASH_CBLOCK);
+
+#ifndef HASH_MAKE_STRING
+# error "HASH_MAKE_STRING must be defined!"
+#else
+ HASH_MAKE_STRING(c, md);
+#endif
+
+ return 1;
+}
+
+#ifndef MD32_REG_T
+# if defined(__alpha) || defined(__sparcv9) || defined(__mips)
+# define MD32_REG_T long
+/*
+ * This comment was originally written for MD5, which is why it
+ * discusses A-D. But it basically applies to all 32-bit digests,
+ * which is why it was moved to common header file.
+ *
+ * In case you wonder why A-D are declared as long and not...