[openssl.org #220] bug in config (openssl-0.9.6g, Solaris2.6)

2002-11-14 Thread Richard Levitte via RT

This ticket is now resolved.

[levitte - Fri Oct 11 10:18:21 2002]:

 This ticket appears to be resolvable, but to be safe, I'll ask: is
 this still an issue?
 
 [guest - Fri Aug 16 11:04:41 2002]:
 
   Note that the solaris-sparcv9-cc and solaris-sparcv9-gcc
  configurations
   actually use just sparcv8plus code (32 bit); see Configure.
 
  I did not know that, since I looked at config only, but not at
  Configure. But still: is it assured that every sun4u machine has
 the
  sparcv8plus instruction set? If not, then the patch is still
 required
  as the isalist manpage says: Programs compiled for instruction
 sets
  that do not appear in the list will most likely experience
 perfomance
  degradation or not run at all on this machine.
 
   Only the solari64-sparcv9-... configuration really needs 
sparcv9.
  
   This is on a sun4u machine with 32-bit OS only:
   $ isalist
   sparcv8plus+vis sparcv8plus sparcv8 sparcv8-fsmuld sparcv7 
sparc
  
   solaris-sparcv9-cc or ...-gcc are the configurations that 
should
 be
  used
   on this machine.
  
   Do you have a sun4u machine on which the solaris-sparcv9-cc/gcc
 code
   actually fails?
 
  I compiled OpenSSL straightaway for sparv8 since I was scared by
 the
  isalist manpage (s. above).
 
  
I agree.  Please try the attached patch
  
   The patch should not be necessary (and should probably be
 reverted
  in
   the CVS).
 


-- 
Richard Levitte
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]



[openssl.org #220] bug in config (openssl-0.9.6g, Solaris2.6)

2002-10-11 Thread Richard Levitte via RT


This ticket appears to be resolvable, but to be safe, I'll ask: is 
this still an issue?

[guest - Fri Aug 16 11:04:41 2002]:

  Note that the solaris-sparcv9-cc and solaris-sparcv9-gcc
 configurations
  actually use just sparcv8plus code (32 bit); see Configure.
 
 I did not know that, since I looked at config only, but not at
 Configure. But still: is it assured that every sun4u machine has 
the
 sparcv8plus instruction set? If not, then the patch is still 
required
 as the isalist manpage says: Programs compiled for instruction 
sets
 that do not appear in the list will most likely experience 
perfomance
 degradation or not run at all on this machine.
 
  Only the solari64-sparcv9-... configuration really needs sparcv9.
 
  This is on a sun4u machine with 32-bit OS only:
  $ isalist
  sparcv8plus+vis sparcv8plus sparcv8 sparcv8-fsmuld sparcv7 sparc
 
  solaris-sparcv9-cc or ...-gcc are the configurations that should 
be
 used
  on this machine.
 
  Do you have a sun4u machine on which the solaris-sparcv9-cc/gcc 
code
  actually fails?
 
 I compiled OpenSSL straightaway for sparv8 since I was scared by 
the
 isalist manpage (s. above).
 
 
   I agree.  Please try the attached patch
 
  The patch should not be necessary (and should probably be 
reverted
 in
  the CVS).


-- 
Richard Levitte
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]



[openssl.org #220] bug in config (openssl-0.9.6g, Solaris2.6)

2002-08-16 Thread via RT


 Note that the solaris-sparcv9-cc and solaris-sparcv9-gcc configurations
 actually use just sparcv8plus code (32 bit); see Configure.

I did not know that, since I looked at config only, but not at Configure. But still: 
is it assured that every sun4u machine has the 
sparcv8plus instruction set? If not, then the patch is still required as the isalist 
manpage says: Programs compiled for instruction sets 
that do not appear in the list will most likely experience perfomance degradation or 
not run at all on this machine.

 Only the solari64-sparcv9-... configuration really needs sparcv9.
 
 This is on a sun4u machine with 32-bit OS only:
 $ isalist
 sparcv8plus+vis sparcv8plus sparcv8 sparcv8-fsmuld sparcv7 sparc
 
 solaris-sparcv9-cc or ...-gcc are the configurations that should be used
 on this machine.
 
 Do you have a sun4u machine on which the solaris-sparcv9-cc/gcc code
 actually fails?

I compiled OpenSSL straightaway for sparv8 since I was scared by the isalist manpage 
(s. above).

 
  I agree.  Please try the attached patch
 
 The patch should not be necessary (and should probably be reverted in
 the CVS).
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]



[openssl.org #220] bug in config (openssl-0.9.6g, Solaris2.6)

2002-08-15 Thread Richard Levitte via RT


[guest - Tue Aug 13 16:21:38 2002]:

 In the case 'sun4u*-*-solaris2 stating on line 567 of file config, 
OUT
 is set to 'solaris-sparcv9-$CC' even if ISA64 does not contain
 sparcv9.
 I do not think this is done deliberately.

Please help us, what should the target be in that case?  
solaris-sparcv8-$CC?

-- 
Richard Levitte
[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]



[openssl.org #220] bug in config (openssl-0.9.6g, Solaris2.6)

2002-08-15 Thread via RT


Since isalist displays the available native instruction sets ordered in the sense of 
best performance, I guess the best choice for target 
would be the leftmost in the list displayed. Under no circumstances should the target 
be set to something which is not available on the 
respective platform. Agree?
Or did I completely misunderstand something there? :-)

giovari

[levitte - Thu Aug 15 11:56:30 2002]:

 [guest - Tue Aug 13 16:21:38 2002]:
 
  In the case 'sun4u*-*-solaris2 stating on line 567 of file config,
 OUT
  is set to 'solaris-sparcv9-$CC' even if ISA64 does not contain
  sparcv9.
  I do not think this is done deliberately.
 
 Please help us, what should the target be in that case?
 solaris-sparcv8-$CC?

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]



[openssl.org #220] bug in config (openssl-0.9.6g, Solaris2.6)

2002-08-15 Thread Richard Levitte via RT


[guest - Thu Aug 15 14:21:45 2002]:

 Since isalist displays the available native instruction sets ordered
 in the sense of best performance, I guess the best choice for target
 would be the leftmost in the list displayed. Under no circumstances
 should the target be set to something which is not available on the
 respective platform. Agree?

I agree.  Please try the attached patch (you might have to go into RT 
to fetch it).

-- 
Richard Levitte
[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]



[openssl.org #220] bug in config (openssl-0.9.6g, Solaris2.6)

2002-08-15 Thread via RT


This patch works perfectly to me, thanks.

giovari

[levitte - Thu Aug 15 16:04:15 2002]:

 [guest - Thu Aug 15 14:21:45 2002]:
 
  Since isalist displays the available native instruction sets ordered
  in the sense of best performance, I guess the best choice for target
  would be the leftmost in the list displayed. Under no circumstances
  should the target be set to something which is not available on the
  respective platform. Agree?
 
 I agree.  Please try the attached patch (you might have to go into RT 
 to fetch it).

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]



[openssl.org #220] bug in config (openssl-0.9.6g, Solaris2.6)

2002-08-15 Thread Bodo Moeller via RT


[levitte - Thu Aug 15 16:04:15 2002]:
 [guest - Thu Aug 15 14:21:45 2002]:

 Since isalist displays the available native instruction sets ordered
 in the sense of best performance, I guess the best choice for target
 would be the leftmost in the list displayed. Under no circumstances
 should the target be set to something which is not available on the
 respective platform. Agree?
 
Note that the solaris-sparcv9-cc and solaris-sparcv9-gcc configurations
actually use just sparcv8plus code (32 bit); see Configure.
Only the solari64-sparcv9-... configuration really needs sparcv9.

This is on a sun4u machine with 32-bit OS only:
$ isalist
sparcv8plus+vis sparcv8plus sparcv8 sparcv8-fsmuld sparcv7 sparc

solaris-sparcv9-cc or ...-gcc are the configurations that should be used
on this machine.

Do you have a sun4u machine on which the solaris-sparcv9-cc/gcc code
actually fails?

 I agree.  Please try the attached patch

The patch should not be necessary (and should probably be reverted in
the CVS).
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]



[openssl.org #220] bug in config (openssl-0.9.6g, Solaris2.6)

2002-08-13 Thread via RT


In the case 'sun4u*-*-solaris2 stating on line 567 of file config, OUT is set to 
'solaris-sparcv9-$CC' even if ISA64 does not contain sparcv9.
I do not think this is done deliberately.

giovari
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]