Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

Morning Dennis, et al This may be off thread topic, but one thing I have noticed with the x86 openssl builds shipped by Oracle and Blastwave in the releases I have been testing FooCrypt against ( 10u11 through 11.3 ) is that openssl seems to ‘HANG’ when inputting a string greater than 262

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 24/02/18 02:18 PM, Erik Forsberg wrote: -- Original Message -- As for -lm, which symbol was undefined? Undefined   first referenced   symbol in file fabs    test/ct_test.o ??? One can only wonder where does

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

>-- Original Message -- > > As for -lm, which symbol was undefined? > Undefined   first referenced   symbol in file fabs    test/ct_test.o >>> >>> ??? One can only wonder where does it come

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

>-- Original Message -- > >>> As for -lm, which symbol was undefined? >>> >> >> Undefined   first referenced >>  symbol in file >> fabs    test/ct_test.o > >??? One can only wonder where does it come from. I see no fabs

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

as that is the ONLY -lm reference and the fact its in test code, why not simply avoid using fabs(), that is so trivial here ? if (value < 0) value = -value; >-- Original Message -- > >On 24/02/18 04:47 AM, Andy Polyakov wrote: >>> So testsuite is running but this is a non-optimal debug

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> As for -lm, which symbol was undefined? > Undefined   first referenced   symbol in file fabs    test/ct_test.o >>> >>> ??? One can only wonder where does it come from. I see no fabs >>>

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

As for -lm, which symbol was undefined? >>> >>> Undefined   first referenced >>>   symbol in file >>> fabs    test/ct_test.o >> >> ??? One can only wonder where does it come from. I see no fabs >> anywhere...

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

In message on Sat, 24 Feb 2018 13:51:45 +0100, Andy Polyakov said: appro> >> As for -lm, which symbol was undefined? appro> >> appro> > appro> > Undefined   first referenced appro> >  symbol   

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

In message on Sat, 24 Feb 2018 06:14:50 -0500, Dennis Clarke said: dclarke> On 24/02/18 05:13 AM, Richard Levitte wrote: dclarke> > In message <607c8d70-4283-1b55-2eac-c9f30a3a3...@blastwave.org> on dclarke> > Sat, 24

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 24/02/18 07:51 AM, Andy Polyakov wrote: As for -lm, which symbol was undefined? Undefined   first referenced  symbol in file fabs    test/ct_test.o ??? One can only wonder where does it come from. I see no fabs

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

>> As for -lm, which symbol was undefined? >> > > Undefined   first referenced >  symbol in file > fabs    test/ct_test.o ??? One can only wonder where does it come from. I see no fabs anywhere... There also was remark

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 24/02/18 05:13 AM, Richard Levitte wrote: In message <607c8d70-4283-1b55-2eac-c9f30a3a3...@blastwave.org> on Sat, 24 Feb 2018 00:24:34 -0500, Dennis Clarke said: dclarke> Not sure why but the various scripts and test files are hell dclarke> bent on using the perl in

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 24/02/18 05:13 AM, Richard Levitte wrote: In message <607c8d70-4283-1b55-2eac-c9f30a3a3...@blastwave.org> on Sat, 24 Feb 2018 00:24:34 -0500, Dennis Clarke said: dclarke> Not sure why but the various scripts and test files are hell dclarke> bent on using the perl in

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 24/02/18 04:47 AM, Andy Polyakov wrote: So testsuite is running but this is a non-optimal debug build and only on the Fujitsu sparc and not on a baseline v9 yet. See "e_flags" in the ELF header below which is somewhat restrictive.   e_flags:    [ EF_SPARCV9_TSO EF_SPARC_SUN_US1

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

In message <607c8d70-4283-1b55-2eac-c9f30a3a3...@blastwave.org> on Sat, 24 Feb 2018 00:24:34 -0500, Dennis Clarke said: dclarke> Not sure why but the various scripts and test files are hell dclarke> bent on using the perl in the system as opposed to what I dclarke> have

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> So testsuite is running but this is a non-optimal debug build and only > on the Fujitsu sparc and not on a baseline v9 yet. See "e_flags" in the > ELF header below which is somewhat restrictive. > >   e_flags:    [ EF_SPARCV9_TSO EF_SPARC_SUN_US1 EF_SPARC_SUN_US3 ] If "somewhat restrictive"

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

I have run into a bit of a snag here. Firstly everything compiles just fine with zero code changes. Zero. All we need are some careful CFLAGS and the compile moves along swimmingly. However the test stage gets terribly wedged just after test 70-test_clienthello.t completes. Not sure why but the

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 21/02/18 04:53 PM, Norm Green wrote: On 2/21/2018 12:46 PM, Andy Polyakov wrote: And "the default for all v9 architectures is -xmemalign=8s". I'm getting confused.  Since I did not specify -xmemalign at all.. Without getting into some needed CFLAGS let me just say that the build ran fine

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

>> And "the default for all v9 architectures is -xmemalign=8s". > I'm getting confused.  Since I did not specify -xmemalign at all, And not specifying -xmemalign is equivalent of specifying 8s in 64-bit build such as one in question. > why > did the test fail with SIGBUS in the first place? 

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 2/21/2018 12:46 PM, Andy Polyakov wrote: And "the default for all v9 architectures is -xmemalign=8s". I'm getting confused.  Since I did not specify -xmemalign at all, why did the test fail with SIGBUS in the first place?  Seems like there should have been no alignment problem if the

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> So really we could do all manner of nasty things here and watch all > manner of performance results and cool coredumps and it would be fun to > try.  However the option -xmemalign=8s will enforce "There should be no > misaligned accesses in the program". And "the default for all v9

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 21/02/18 12:57 PM, Norm Green wrote: On 2/21/2018 9:42 AM, Dennis Clarke wrote: Which is correct way to do this on sparc systems. Why do you say that?  We've been building OpenSSL on SPARC for the past 7 years without that flag and it's worked just fine with only a few minor changes to

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 21/02/18 12:57 PM, Norm Green wrote: On 2/21/2018 9:42 AM, Dennis Clarke wrote: Which is correct way to do this on sparc systems. Why do you say that?  We've been building OpenSSL on SPARC for the past 7 years without that flag and it's worked just fine with only a few minor changes to

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 2/21/2018 9:42 AM, Dennis Clarke wrote: Which is correct way to do this on sparc systems. Why do you say that?  We've been building OpenSSL on SPARC for the past 7 years without that flag and it's worked just fine with only a few minor changes to the compile/link flags. Norm --

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 21/02/18 12:11 PM, Norm Green wrote: > On 2/21/2018 8:42 AM, Dennis Clarke wrote: >> Pretty sure I have done builds and tests. In fact I am certain of it. > > If you added -xmemalign=8s to the SPARC compiler flags (as shown in one > of your emails from yesterday) then you would not see the

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 2/21/2018 8:42 AM, Dennis Clarke wrote: Pretty sure I have done builds and tests. In fact I am certain of it. If you added -xmemalign=8s to the SPARC compiler flags (as shown in one of your emails from yesterday) then you would not see the problem.  -xmemalign=8s forces the compiler to

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> On Feb 21, 2018, at 11:42 AM, Dennis Clarke wrote: > > On 21/02/18 09:14 AM, Viktor Dukhovni wrote: >>> On Feb 21, 2018, at 5:06 AM, Andy Polyakov wrote: >>> >>> I wonder how come the problem with asn1_encode_test.c went unnoticed so >>> far.

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 21/02/18 09:14 AM, Viktor Dukhovni wrote: On Feb 21, 2018, at 5:06 AM, Andy Polyakov wrote: I wonder how come the problem with asn1_encode_test.c went unnoticed so far. Objects on stack are customarily aligned at pointer size, even if their declaration doesn't imply

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> On Feb 21, 2018, at 5:06 AM, Andy Polyakov wrote: > > I wonder how come the problem with asn1_encode_test.c went unnoticed so > far. Objects on stack are customarily aligned at pointer size, even if > their declaration doesn't imply corresponding guarantee. So there are >

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> https://github.com/openssl/openssl/pull/5423 I wonder how come the problem with asn1_encode_test.c went unnoticed so far. Objects on stack are customarily aligned at pointer size, even if their declaration doesn't imply corresponding guarantee. So there are two options here: a) it's first time

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> Interesting comment : > > > Solaris x86 with Sun C setups >     # There used to be solaris-x86-cc target, but it was removed, >     # primarily because vendor assembler can't assemble our modules >     # with -KPIC flag. As result it, assembly support, was not even >     # available as

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

In message <6088d4cb-7566-c216-1e28-0892641cd...@blastwave.org> on Tue, 20 Feb 2018 21:17:32 -0500, Dennis Clarke said: dclarke> Have to dig around and see what LDCMD was intended to be. LDCMD is a convenience variable for some users to specify a different command than

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

https://github.com/openssl/openssl/pull/5423 On 2/20/18, 2:10 PM, "Salz, Rich via openssl-users" wrote: I agree, let's just use malloc for the reasons you said. PR later today. On 2/20/18, 2:08 PM, "Viktor Dukhovni" wrote:

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 20/02/18 01:36 PM, Norm Green wrote: Hi Dennis, You're right, I did modify the config file... I have managed to get to the link stage here and ran into some odd syntax issue. Have to dig around and see what LDCMD was intended to be. ${LDCMD:-/opt/developerstudio12.6/bin/cc}

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 20/02/18 01:52 PM, Salz, Rich via openssl-users wrote: So ... this will be fun. :) Thanks for poking at this, folks. Please take a look at the INSTALL and README files which do cover some of this prerequisites. And then once you've "fixed" it, let us know what we need to

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 20/02/18 02:06 PM, Erik Forsberg wrote: -- Original Message -- On 20/02/18 12:47 PM, Norm Green wrote: On 2/20/2018 5:43 AM, Michael Wojcik wrote: <... snippage ...> I also tried building with c99 instead of cc, without success. I build my Solaris OpenSSL binaries using studo

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

>-- Original Message -- > >On 20/02/18 12:47 PM, Norm Green wrote: >> On 2/20/2018 5:43 AM, Michael Wojcik wrote: >>> Not by default. The comments in /usr/include/sys/feature_tests.h (on a >>> Solaris system) explain this in excruciating detail, but in short you >>> need either

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

I agree, let's just use malloc for the reasons you said. PR later today. On 2/20/18, 2:08 PM, "Viktor Dukhovni" wrote: > On Feb 20, 2018, at 11:36 AM, Norm Green wrote: > > Your patch tests clean, however

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> On Feb 20, 2018, at 11:36 AM, Norm Green > wrote: > > Your patch tests clean, however there is an easier way which avoids malloc: Great, so it was the unaligned "buf". Great. As for malloc vs. tricks to align the stack-based array, I see little need to

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 20/02/18 01:50 PM, Dennis Clarke wrote: On 20/02/18 01:36 PM, Norm Green wrote: Making progress here ... /opt/developerstudio12.6/bin/c99 -I. -Icrypto/include -Iinclude -errfmt=error -erroff=%none -errshort=full -xstrconst -xildoff -m64 -xmemalign=8s -xnolibmil -Xc -xcode=pic32

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> So ... this will be fun. :) Thanks for poking at this, folks. Please take a look at the INSTALL and README files which do cover some of this prerequisites. And then once you've "fixed" it, let us know what we need to change!! -- openssl-users mailing list To unsubscribe:

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 20/02/18 01:36 PM, Norm Green wrote: Hi Dennis, You're right, I did modify the config file, sorry.  I did it so long ago I had forgotten.  I will email it to you shortly. Not a problem .. everyone does. I mean look at this mess if you don't : corv $ ./Configure shared zlib threads

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

Hi Dennis, You're right, I did modify the config file, sorry.  I did it so long ago I had forgotten.  I will email it to you shortly. Norm On 2/20/2018 10:14 AM, Dennis Clarke wrote: On 20/02/18 01:11 PM, Norm Green wrote: Just download and build v1.1.1 pre alpha 1 on Solaris.  It's on

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 20/02/18 01:11 PM, Norm Green wrote: Just download and build v1.1.1 pre alpha 1 on Solaris.  It's on ftp.openssl.org.  That's all I did.  Configure using solaris64-sparcv9-cc .  I'm using Solaris studio 12.3. Let's have a look. corv $ uname -a SunOS corv 5.10 Generic_150400-59 sun4u

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 20/02/18 01:11 PM, Norm Green wrote: Just download and build v1.1.1 pre alpha 1 on Solaris.  It's on ftp.openssl.org.  That's all I did.  Configure using solaris64-sparcv9-cc .  I'm using Solaris studio 12.3. Did you modify the Configure file ? Last time I looked the CFLAGS as well as

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

Just download and build v1.1.1 pre alpha 1 on Solaris.  It's on ftp.openssl.org.  That's all I did.  Configure using solaris64-sparcv9-cc .  I'm using Solaris studio 12.3. Norm On 2/20/2018 10:01 AM, Dennis Clarke wrote: On 20/02/18 12:47 PM, Norm Green wrote: On 2/20/2018 5:43 AM, Michael

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 20/02/18 12:47 PM, Norm Green wrote: On 2/20/2018 5:43 AM, Michael Wojcik wrote: Not by default. The comments in /usr/include/sys/feature_tests.h (on a Solaris system) explain this in excruciating detail, but in short you need either -DPOSIX_C_SOURCE=200112L or -D_XOPEN_SOURCE=600 (or the

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 2/20/2018 5:43 AM, Michael Wojcik wrote: Not by default. The comments in /usr/include/sys/feature_tests.h (on a Solaris system) explain this in excruciating detail, but in short you need either -DPOSIX_C_SOURCE=200112L or -D_XOPEN_SOURCE=600 (or the equivalent in the code) to compile with

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

Hi Viktor, Your patch tests clean, however there is an easier way which avoids malloc: Norm Index: test/asn1_encode_test.c === --- test/asn1_encode_test.c (revision 43654) +++ test/asn1_encode_test.c (working copy) @@

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf > Of Norm Green > Sent: Monday, February 19, 2018 17:02 > To: Benjamin Kaduk; openssl-users@openssl.org > Subject: Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC > > For the failure in

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On Tue, Feb 20, 2018 at 01:26:02PM +, Salz, Rich via openssl-users wrote: > Would making buf a union also avoid the problem? > > union { unsigned long dummy[2]; char buf[DATA_BUF_SIZE]; } d > and then replace 'buf' with 'd.buf' in the code? If alignment of "buf" is the issue, then yes,

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

Would making buf a union also avoid the problem? union { unsigned long dummy[2]; char buf[DATA_BUF_SIZE]; } d and then replace 'buf' with 'd.buf' in the code? On 2/20/18, 12:00 AM, "Viktor Dukhovni" wrote: On Mon, Feb 19, 2018 at 01:45:26PM -0800, Norm

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On Mon, Feb 19, 2018 at 01:45:26PM -0800, Norm Green wrote: > # ASN1_LONG_DATA: > #   success: TRUE > t@1 (l@1) signal BUS (invalid address alignment) in asn1_item_print_ctx at > line 155 in file "tasn_prn.c" >   155  || (it->utype != V_ASN1_BOOLEAN)) && *fld == NULL) { Perhaps aligning

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

For the failure in secmemtst, it appears that secure memory is not enabled per this code in ./crypto/mem_sec.c  23 /* e_os.h includes unistd.h, which defines _POSIX_VERSION */  24 #if !defined(OPENSSL_NO_SECURE_MEMORY) && defined(OPENSSL_SYS_UNIX) \  25 && defined(_POSIX_VERSION) &&

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

You are correct, we are getting a SIGBUS.  Solaris SPARC does not allow unaligned data access: (dbx) run Running: asn1_encode_test (process id 11159) Reading libc_psr.so.1 Reading libscf.so.1 Reading libdoor.so.1 Reading libuutil.so.1 Reading libgen.so.1 Reading libmd.so.1 Reading libmp.so.2

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

> On Feb 19, 2018, at 4:20 PM, Norm Green wrote: > > /export/localnew/sparc.Solaris/bin/gmake depend && > /export/localnew/sparc.Solaris/bin/gmake _tests > gmake[1]: Entering directory > '/hamburg4/users/normg/gs64trunk/slow10/openssl_1.1' > gmake[1]: Leaving

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

The output is not too long. /export/localnew/sparc.Solaris/bin/gmake depend && /export/localnew/sparc.Solaris/bin/gmake _tests gmake[1]: Entering directory '/hamburg4/users/normg/gs64trunk/slow10/openssl_1.1' gmake[1]: Leaving directory '/hamburg4/users/normg/gs64trunk/slow10/openssl_1.1'

Re: [openssl-users] 1.1.1 pre1 tests failing on Solaris SPARC

On 02/19/2018 02:06 PM, Norm Green wrote: > Not sure if this is expected on this platform? > > Test Summary Report > --- > ../test/recipes/04-test_asn1_encode.t    (Wstat: 256 Tests: 1 > Failed: 1) >   Failed test:  1 >   Non-zero exit status: 1 >