public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/16462] New: [3.5 Regression] New fails forgcc.c-torture/execute/builtins/strpcpy-2.c Date: Fri, 09 Jul 2004 21:23:00 -0000 [thread overview] Message-ID: <20040709212319.16462.danglin@gcc.gnu.org> (raw) FAIL: gcc.c-torture/execute/builtins/strpcpy-2.c execution, -O0 FAIL: gcc.c-torture/execute/builtins/strpcpy-2.c execution, -O1 FAIL: gcc.c-torture/execute/builtins/strpcpy-2.c execution, -O2 FAIL: gcc.c-torture/execute/builtins/strpcpy-2.c execution, -O3 -fomit-frame-po inter FAIL: gcc.c-torture/execute/builtins/strpcpy-2.c execution, -O3 -g FAIL: gcc.c-torture/execute/builtins/strpcpy-2.c execution, -Os also FAIL: gcc.c-torture/execute/builtins/strpcpy.c execution, -O1 FAIL: gcc.c-torture/execute/builtins/strpcpy.c execution, -O2 FAIL: gcc.c-torture/execute/builtins/strpcpy.c execution, -O3 -fomit-frame-poin ter FAIL: gcc.c-torture/execute/builtins/strpcpy.c execution, -O3 -g FAIL: gcc.c-torture/execute/builtins/strpcpy.c execution, -Os Executing on host: /home/dave/gnu/gcc-3.5/objdir/gcc/xgcc -B/home/dave/gnu/gcc-3 .5/objdir/gcc/ /home/dave/gnu/gcc-3.5/gcc/gcc/testsuite/gcc.c-torture/execute/bu iltins/strpcpy-2.c /home/dave/gnu/gcc-3.5/gcc/gcc/testsuite/gcc.c-torture/execut e/builtins/strpcpy-2-lib.c /home/dave/gnu/gcc-3.5/gcc/gcc/testsuite/gcc.c-tortur e/execute/builtins/lib/main.c -w -O0 -lm -o /home/dave/gnu/gcc-3.5/objdir/ gcc/testsuite/strpcpy-2.x0 (timeout = 300) PASS: gcc.c-torture/execute/builtins/strpcpy-2.c compilation, -O0 Setting LD_LIBRARY_PATH to :/home/dave/gnu/gcc-3.5/objdir/bfd:/home/dave/gnu/gcc -3.5/objdir/opcodes:/home/dave/gnu/gcc-3.5/objdir/hppa-linux/libstdc++-v3/src/.l ibs:/home/dave/gnu/gcc-3.5/objdir/hppa-linux/libmudflap/.libs:/home/dave/opt/gnu /gcc/gcc-3.5/lib FAIL: gcc.c-torture/execute/builtins/strpcpy-2.c execution, -O0 We have the following: Breakpoint 1, 0x40748cd8 in abort () from /lib/libc.so.6 (gdb) bt #0 0x40748cd8 in abort () from /lib/libc.so.6 #1 0x0001067c in test (buf3=0x20f68, buf4=0x20fe8 "", buf6=0x10c8c "rstuvwxyz", n=0) at /home/dave/gnu/gcc-3.5/gcc/gcc/testsuite/gcc.c-torture/execute/builtins/strpcpy-2.c:26 #2 0x00010814 in main_test () at /home/dave/gnu/gcc-3.5/gcc/gcc/testsuite/gcc.c-torture/execute/builtins/strpcpy-2.c:44 #3 0x000108d0 in main () at /home/dave/gnu/gcc-3.5/gcc/gcc/testsuite/gcc.c-torture/execute/builtins/lib/main.c:8 The tests were ok on July 8 <http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg00365.html>. -- Summary: [3.5 Regression] New fails forgcc.c- torture/execute/builtins/strpcpy-2.c Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: critical Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: danglin at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: hppa-unknown-linux-gnu GCC host triplet: hppa-unknown-linux-gnu GCC target triplet: hppa-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16462
next reply other threads:[~2004-07-09 21:23 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-09 21:23 danglin at gcc dot gnu dot org [this message] 2004-07-09 21:29 ` [Bug middle-end/16462] " pinskia at gcc dot gnu dot org 2004-07-10 2:28 ` pinskia at gcc dot gnu dot org
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=20040709212319.16462.danglin@gcc.gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).