public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19745] [meta-bug]: cris-elf gcc, g++, objc testsuite failures as of "Tue Feb  1 22:03:59 UTC 2005"
Date: Wed, 09 Feb 2005 07:23:00 -0000	[thread overview]
Message-ID: <20050208214505.14907.qmail@sourceware.org> (raw)
In-Reply-To: <20050202010250.19745.hp@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-02-08 21:45 -------
WARNING: gcc.dg/20010912-1.c compilation failed to produce executable
as the following is in the testcase:
/* { dg-warning "not supported" "PIC unsupported" { target cris-*-elf* cris-*-aout* mmix-*-* } 0 } */

FAIL: gcc.dg/20020430-1.c (test for excess errors)
FAIL: gcc.dg/20021018-1.c (test for excess errors)
FAIL: gcc.dg/20021023-1.c (test for excess errors)
FAIL: gcc.dg/20021029-1.c (test for excess errors)
FAIL: gcc.dg/20030702-1.c (test for excess errors)
FAIL: gcc.dg/20030708-1.c (test for excess errors)
uses -fpic just like gcc.dg/20010912-1.c

I am starting to think there should be a require-pic in the testsuite.


-- 


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


  parent reply	other threads:[~2005-02-08 21:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02  1:03 [Bug target/19745] New: meta: " hp at gcc dot gnu dot org
2005-02-02  3:32 ` [Bug target/19745] " hp at gcc dot gnu dot org
2005-02-08 21:53 ` hp at gcc dot gnu dot org
2005-02-09  2:29 ` [Bug target/19745] [meta-bug]: " pinskia at gcc dot gnu dot org
2005-02-09  7:16 ` hp at gcc dot gnu dot org
2005-02-09  7:23 ` pinskia at gcc dot gnu dot org [this message]
2005-02-10 13:54 ` hp at gcc dot gnu dot org
2005-02-27 19:45 ` hp at gcc dot gnu dot org
2005-02-27 19:47 ` hp at gcc dot gnu dot org
     [not found] <bug-19745-507@http.gcc.gnu.org/bugzilla/>
2007-03-29 12:00 ` steven 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=20050208214505.14907.qmail@sourceware.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).