public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ghazi@caip.rutgers.edu
To: gcc-gnats@gcc.gnu.org
Cc: davem@redhat.com
Subject: target/6540: sparc-sun-solaris2.7 (perhaps all bi-arch sparc) fail libstdc++-v3 18_support/numeric_limits.cc
Date: Thu, 02 May 2002 09:06:00 -0000	[thread overview]
Message-ID: <20020502155636.1325.qmail@sources.redhat.com> (raw)


>Number:         6540
>Category:       target
>Synopsis:       sparc-sun-solaris2.7 (perhaps all bi-arch sparc) fail libstdc++-v3 18_support/numeric_limits.cc
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 02 09:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Kaveh Ghazi
>Release:        gcc version 3.1 20020501 (prerelease)
>Organization:
>Environment:
sparc-sun-solaris2.7 native as/ld
>Description:
The libstdc++-v3 test 18_support/numeric_limits.cc fails on sparc-sun-solaris2.7 for -m32 but succeeds for -m64 as seen here:
http://gcc.gnu.org/ml/gcc-testresults/2002-05/msg00028.html
http://gcc.gnu.org/ml/gcc-testresults/2002-05/msg00048.html
It passes on sparcv9:
http://gcc.gnu.org/ml/gcc-testresults/2002-05/msg00003.html

On my solaris2.7 system, it fails on the long double test_extrema.  I tracked this down to the definition of LDBL_MIN/LDBL_MAX from gcc/config/float-sparc.h.  In there, we define a 128 bit LDBL_* only if sparcv9 or arch64 are defined.  However sol2-bi.h hardcodes LONG_DOUBLE_TYPE_SIZE to 128.

So this is really a bug in the float.h that gets generated for solaris2.7.  Using this program to demonstrate:

#include <stdio.h>
#include <float.h>
int main()
{
  long double min = LDBL_MIN, max = LDBL_MAX;
  printf ("%d\n%Le\n%Le\n", (int) sizeof(long double), min, max);
  return 0;
}

If I compile with -m32, I get:
16
2.225074e-308
1.797693e+308

If I compile with -m64, I get:
16
3.362103e-4932
1.189731e+4932

IMHO, I should get the latter result for both cases.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-02 16:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02  9:06 ghazi [this message]
2002-05-02 14:59 davem

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=20020502155636.1325.qmail@sources.redhat.com \
    --to=ghazi@caip.rutgers.edu \
    --cc=davem@redhat.com \
    --cc=gcc-gnats@gcc.gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).