public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/6300: [PATCH] sparcv9-sun-solaris2.7 gcc-3.1 C testsuite failure in gcc.dg/cpp/charconst.c Date: Mon, 22 Apr 2002 00:26:00 -0000 [thread overview] Message-ID: <20020422072604.31464.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6300; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> Cc: gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org, neil@daikokuya.demon.co.uk Subject: Re: c/6300: [PATCH] sparcv9-sun-solaris2.7 gcc-3.1 C testsuite failure in gcc.dg/cpp/charconst.c Date: Mon, 22 Apr 2002 00:25:33 -0700 On Sun, Apr 21, 2002 at 06:24:15PM -0700, Zack Weinberg wrote: > The cure is to call convert() to the proper type from lex_charconst, > instead of just smashing the type field. I am bootstrapping the > appended change now. If you could test it on solaris, I'd appreciate > it. Here's testsuite results for i686-linux (3.1 branch). I believe they indicate no new regressions for this change. zw === libstdc++-v3 tests === FAIL: 26_numerics/c99_classification_macros_c.cc (test for excess errors) === libstdc++-v3 Summary === # of expected passes 372 # of unexpected failures 1 # of expected failures 25 === libjava tests === === libjava Summary === # of expected passes 2075 # of expected failures 18 # of untested testcases 14 === gcc tests === FAIL: gcc.c-torture/execute/20020307-2.c execution, -O1 FAIL: gcc.c-torture/execute/20020307-2.c execution, -O2 FAIL: gcc.c-torture/execute/20020307-2.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/20020307-2.c execution, -O3 -fomit-frame-pointer -funroll-loops FAIL: gcc.c-torture/execute/20020307-2.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions FAIL: gcc.c-torture/execute/20020307-2.c execution, -O3 -g FAIL: gcc.c-torture/execute/20020402-1.c execution, -Os === gcc Summary === # of expected passes 18315 # of unexpected failures 7 # of expected failures 66 # of unsupported tests 43 === g++ tests === === g++ Summary === # of expected passes 7168 # of expected failures 86 # of untested testcases 9 # of unsupported tests 3 === g77 tests === === g77 Summary === # of expected passes 1468 === objc tests === === objc Summary === # of expected passes 1036 # of expected failures 6 zw
next reply other threads:[~2002-04-22 7:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-22 0:26 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-22 14:46 Zack Weinberg 2002-04-22 12:46 Kaveh R. Ghazi 2002-04-22 10:06 Neil Booth 2002-04-22 0:36 Zack Weinberg 2002-04-21 23:56 Neil Booth 2002-04-21 18:26 Zack Weinberg
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=20020422072604.31464.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).