Hi,
If anyone has run my findsyms perl script..
http://lists.debian.org/debian-glibc/2002/debian-glibc-200209/msg00148.html
http://lists.debian.org/debian-glibc/2002/debian-glibc-200209/msg00164.html
...and has results for a particular arch, they may want to share this
information upstream wit
Package: gcc
Running Debian unstable on PA-RISC platform (C160 Workstation with 160MHz
PA-8000 CPU)
Compiling openssl 0.9.6g with any level of optimization for PA1.1 produces
code that passes all tests ("make test") and benchmarks ("openssl speed")
successfully. Using -march=2.0 flag produces c
Greetings!
One more observation here which may be helpful -- on hppa, malloced
memory starts at ~ 0x20 and the stack counts *up* from ~
0xb000. gcl can deal with this without difficulty, except for
the fact that variables declared *volatile* have addresses in the
0x7a range. This pu
forwarded to bts for the record...
- Forwarded message from John David Anglin <[EMAIL PROTECTED]> -
Subject: Re: [parisc-linux] FWD: Bug#162690: [parisc]gcc 3.x produces openssl
test code that SEGVs with -march=2.0 and optimization >0
To: [EMAIL PROTECTED]
From: "John David Anglin" <[EM
4 matches
Mail list logo