public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tenm078902@sanyo.co.jp To: gcc-gnats@gcc.gnu.org Subject: other/10810: gcc-3.3 fails make check Date: Fri, 16 May 2003 03:56:00 -0000 [thread overview] Message-ID: <20030516035552.32579.qmail@sources.redhat.com> (raw) >Number: 10810 >Category: other >Synopsis: gcc-3.3 fails make check >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri May 16 03:56:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Takaharu Tenma >Release: gcc-3.3 >Organization: >Environment: HP-B2600 Workstation HPUX11.00 (hppa2.0w-hp-hpux11.00) >Description: make check fails at test-demangle line 791 as: ./test-demangle < ../../../libiberty/testsuite/demangle-expected FAIL at line 791, style gnu: in: __cl__C11VHDLLibraryGt4PixX3Z11VHDLLibraryZ14VHDLLibraryRepZt4List1Z10VHDLEntity@ out: exp: VHDLLibrary::operator()(PixX<VHDLLibrary, VHDLLibraryRep, List<VHDLEntity> >) const ./test-demangle: 649 tests, 1 failures >How-To-Repeat: build gcc-3.3 and run make check >Fix: This test (line791) contains 80 chars, overruns the buffer in test-demangle.c diff -u2 /home/tenma/gcc-3.3/libiberty/testsuite/test-demangle.c.\~1\~ /home/tenma/gcc-3.3/libiberty/testsuite/test-demangle.c --- /home/tenma/gcc-3.3/libiberty/testsuite/test-demangle.c.~1~ Thu Sep 12 04:58:02 2002 +++ /home/tenma/gcc-3.3/libiberty/testsuite/test-demangle.c Fri May 16 12:37:29 2003 @@ -38,5 +38,5 @@ /* Safely read a single line of arbitrary length from standard input. */ -#define LINELEN 80 +#define LINELEN 160 static void >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-05-16 3:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030516035552.32579.qmail@sources.redhat.com \ --to=tenm078902@sanyo.co.jp \ --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: 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).