public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ghazi@caip.rutgers.edu
To: gcc-gnats@gcc.gnu.org
Cc: zack@codesourcery.com, neil@daikokuya.demon.co.uk
Subject: c/6300: sparcv9-sun-solaris2.7 gcc-3.1 C testsuite failure in gcc.dg/cpp/charconst.c
Date: Sun, 14 Apr 2002 09:26:00 -0000	[thread overview]
Message-ID: <20020414162032.14698.qmail@sources.redhat.com> (raw)


>Number:         6300
>Category:       c
>Synopsis:       sparcv9-sun-solaris2.7 gcc-3.1 C testsuite failure in gcc.dg/cpp/charconst.c
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 14 09:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Kaveh Ghazi
>Release:        gcc version 3.1 20020413 (prerelease)
>Organization:
>Environment:
sparcv9-sun-solaris2.7 native as/ld
>Description:
Testresult:

 > FAIL: gcc.dg/cpp/charconst.c (test for excess errors)

>From gcc.log, the excess error is:

 > Excess errors:
 > gcc.dg/cpp/charconst.c:28: warning: overflow in implicit constant conversion

It seems that sparcv9- (i.e. not sparc-) is necessary to trigger the bug.  See:
http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg00484.html
vs:
http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg00482.html

*** This is a regression from 3.0.3.

>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2002-04-14 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-14  9:26 ghazi [this message]
2002-04-15 11:16 Neil Booth
2002-04-15 14:06 Kaveh R. Ghazi
2002-04-16 17:26 Kaveh R. Ghazi
2002-04-20 14:26 Zack Weinberg
2002-04-21 15:16 Kaveh R. Ghazi

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=20020414162032.14698.qmail@sources.redhat.com \
    --to=ghazi@caip.rutgers.edu \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=neil@daikokuya.demon.co.uk \
    --cc=zack@codesourcery.com \
    /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).