From: "H.Merijn Brand" <h.m.brand@xs4all.nl>
To: Michal Rokos <michal@rokos.cz>
Cc: git@vger.kernel.org
Subject: Re: libcrypto core dump in 64bit
Date: Tue, 12 Feb 2008 17:38:42 +0100 [thread overview]
Message-ID: <20080212173842.0a3704b1@pc09.procura.nl> (raw)
In-Reply-To: <loom.20080212T152138-849@post.gmane.org>
On Tue, 12 Feb 2008 15:26:16 +0000 (UTC), Michal Rokos <michal@rokos.cz>
wrote:
> Hello,
>
> H.Merijn Brand <h.m.brand <at> xs4all.nl> writes:
> > On Mon, 11 Feb 2008 22:42:16 +0000 (GMT), Johannes Schindelin
> > <Johannes.Schindelin <at> gmx.de> wrote:
> > > > #0 0xc0000000033c8940:0 in sha1_block_asm_host_order+0x22e0 ()
> > > > from /usr/local/ssl/lib/libcrypto.so
> > >
> > > This seems to be an OpenSSL issue, probably in its Itanium-optimised code
> > > (since Itanium is not _all_ that common, it is quite likely that no many
> > > people exercise this part of the code).
> >
> > Now tried with HP C-ANSI-C -O3, -O2, -O1, and -O0 and with GNU gcc 4.2.1 -O3
> > All give the same failure
> >
> > > Unfortunately, I am not at all an expert in Itanium's assembler, otherwise
> > > I'd try to help...
>
> yes, this is OpenSSL issue. I had to recompile OpenSSL myself to make it work
> (with no-asm option)
OK, I did the same now, and the docs tell me to turn down optimization to
+O2 when you choose to do so.
Apart from that, when you create shared libs, the default build creates a
conflicting situation, so you have to throw away the files that cause dup
names: aes-ia64.o rc4-ia64.o bn-ia64.o from libcrypto.a
t5302-pack-index.sh now passes
> I'm using only HP cc for building git (with all the toolchain). (No gcc here)
>
> # uname -mrs
> HP-UX B.11.23 ia64
> # cc --version
> cc: HP C/aC++ B3910B A.06.14 [Feb 22 2007]
HP-UX 11.23/64 U rx1620/64 Itanium 2/1600(2) ia64 2037 Mb
cc: HP C/aC++ B3910B A.06.15 [May 16 2007]
Did you get the full test suite to pass?
--
H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using & porting perl 5.6.2, 5.8.x, 5.10.x on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin. http://qa.perl.org
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org
http://www.goldmark.org/jeff/stupid-disclaimers/
next prev parent reply other threads:[~2008-02-12 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 10:28 libcrypto core dump in 64bit H.Merijn Brand
2008-02-11 22:42 ` Johannes Schindelin
2008-02-12 14:06 ` H.Merijn Brand
2008-02-12 15:26 ` Michal Rokos
2008-02-12 16:38 ` H.Merijn Brand [this message]
2008-02-13 9:04 ` Michal Rokos
2008-02-13 10:57 ` H.Merijn Brand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080212173842.0a3704b1@pc09.procura.nl \
--to=h.m.brand@xs4all.nl \
--cc=git@vger.kernel.org \
--cc=michal@rokos.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).