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 ada/27243]  New: FAIL:   c37215h
Date: Fri, 21 Apr 2006 23:21:00 -0000	[thread overview]
Message-ID: <bug-27243-276@http.gcc.gnu.org/bugzilla/> (raw)

gnatlink c37215h.ali --GCC=/home/dave/gcc-4.2/objdir/gcc/xgcc
-B/home/dave/gcc-4
.2/objdir/gcc/
RUN c37215h

,.,. C37215H ACATS 2.5 06-04-21 06:37:47
---- C37215H THE DISCRIMINANT VALUES OF AN INDEX CONSTRAINT ARE PROPERLY
                CHECK FOR COMPATIBILITY WHEN THE DISCRIMINANT IS DEFINED
                BY DEFAULT AND THE COMPONENT IS AND IS NOT PRESENT IN
                THE SUBTYPE.
   * C37215H X VALUE INCORRECT - 13.
**** C37215H FAILED ****************************.
FAIL:   c37215h


-- 
           Summary: FAIL:   c37215h
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ada
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin 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=27243


             reply	other threads:[~2006-04-21 23:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 23:21 danglin at gcc dot gnu dot org [this message]
2006-06-11 20:05 ` [Bug ada/27243] " danglin at gcc dot gnu dot org
2006-06-18 10:58 ` [Bug ada/27243] ACATS: c37215h on hppa-linux laurent at guerby dot net
2006-06-19  3:08 ` dave at hiauly1 dot hia dot nrc dot ca
2007-09-30 16:32 ` danglin at gcc dot gnu dot org
2008-11-17 18:50 ` [Bug ada/27243] [4.2 regression] ACATS c37215h fails ebotcazou 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=bug-27243-276@http.gcc.gnu.org/bugzilla/ \
    --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).