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/15941] New: [regression 3.4.1] new fails gcc.dg/compat/struct-by-value-11 and gcc.dg/compat/struct-by-value-1
Date: Fri, 11 Jun 2004 16:07:00 -0000	[thread overview]
Message-ID: <20040611160703.15941.danglin@gcc.gnu.org> (raw)

The following new fails occured
Executing on host: /xxx/gnu/gcc-3.4/objdir/gcc/xgcc -B/xxx/gnu/gcc-3.4/objdir/gc
c/ c_compat_main_tst.o c_compat_x_tst.o c_compat_y_tst.o     -lm   -o gcc-dg-com
pat-struct-by-value-11-01    (timeout = 300)
PASS: gcc.dg/compat/struct-by-value-11 c_compat_x_tst.o-c_compat_y_tst.o link
Setting LD_LIBRARY_PATH to :/usr/openwin/lib
FAIL: gcc.dg/compat/struct-by-value-11 c_compat_x_tst.o-c_compat_y_tst.o execute

Executing on host: /xxx/gnu/gcc-3.4/objdir/gcc/xgcc -B/xxx/gnu/gcc-3.4/objdir/gc
c/ c_compat_main_tst.o c_compat_x_tst.o c_compat_y_tst.o     -lm   -o gcc-dg-com
pat-struct-by-value-1-01    (timeout = 300)
PASS: gcc.dg/compat/struct-by-value-1 c_compat_x_tst.o-c_compat_y_tst.o link
Setting LD_LIBRARY_PATH to :/usr/openwin/lib
FAIL: gcc.dg/compat/struct-by-value-1 c_compat_x_tst.o-c_compat_y_tst.o execute

This is for

-bash-2.05b$ ../xgcc -B../ -v
Reading specs from ../specs
Configured with: ../gcc/configure --with-gnu-as --with-as=/opt/gnu/bin/as
--enable-shared --with-local-prefix=/opt/gnu --prefix=/opt/gnu/gcc/gcc-3.4.1
--enable-debug=no --disable-nls
Thread model: single
gcc version 3.4.1 20040609 (prerelease)

-- 
           Summary: [regression 3.4.1] new fails gcc.dg/compat/struct-by-
                    value-11 and gcc.dg/compat/struct-by-value-1
           Product: gcc
           Version: 3.4.1
            Status: UNCONFIRMED
          Severity: normal
          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: hppa2.0-hp-hpux11.00
  GCC host triplet: hppa2.0-hp-hpux11.00
GCC target triplet: hppa2.0-hp-hpux11.00


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15941


             reply	other threads:[~2004-06-11 16:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-11 16:07 danglin at gcc dot gnu dot org [this message]
2004-06-11 16:29 ` [Bug target/15941] [3.4 regression] " pinskia at gcc dot gnu dot org
2004-06-11 16:45 ` giovannibajo at libero dot it
2004-06-11 16:59 ` mmitchel at gcc dot gnu dot org
2004-06-11 20:52 ` dave at hiauly1 dot hia dot nrc dot ca
2004-06-11 20:55 ` [Bug target/15941] [3.4/3.5 " pinskia at gcc dot gnu dot org
2004-06-11 21:26 ` dave at hiauly1 dot hia dot nrc dot ca
2004-06-12 16:13 ` danglin at gcc dot gnu dot org
2004-06-12 19:02 ` rth at redhat dot com
2004-06-12 20:43 ` dave at hiauly1 dot hia dot nrc dot ca
2004-06-12 21:37 ` dave at hiauly1 dot hia dot nrc dot ca
2004-06-18  2:48 ` danglin at gcc dot gnu dot org
2004-06-18  4:06 ` danglin at gcc dot gnu dot org
2004-06-18 19:41 ` rth at gcc dot gnu dot org
2004-06-19 17:49 ` mmitchel at gcc dot gnu dot org
2004-06-19 19:25 ` cvs-commit at gcc dot gnu dot org
2004-06-19 19:49 ` cvs-commit at gcc dot gnu dot org
2004-06-19 19:50 ` danglin 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=20040611160703.15941.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: 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).