public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "laurent at guerby dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/18819] [4.1/4.2 Regression] ACATS cdd2a01 cdd2a02 fail at runtime
Date: Sat, 21 Jan 2006 09:32:00 -0000 [thread overview]
Message-ID: <20060121093213.18173.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18819-7210@http.gcc.gnu.org/bugzilla/>
------- Comment #15 from laurent at guerby dot net 2006-01-21 09:32 -------
4.2 fails on amd64-linux as of Fri Jan 20 20:40:28 UTC 2006 (revision 110036)
http://gcc.gnu.org/ml/gcc-testresults/2006-01/msg01071.html
RUN cdd2a02
,.,. CDD2A02 ACATS 2.5 06-01-23 01:01:16
---- CDD2A02 Check that the Read, Write, Input, and Output attributes
are inherited for untagged derived types.
* CDD2A02 Inherited Input and Output are not inverses of each other -
4.
**** CDD2A02 FAILED ****************************.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18819
next prev parent reply other threads:[~2006-01-21 9:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18819-7210@http.gcc.gnu.org/bugzilla/>
2005-10-22 21:51 ` [Bug ada/18819] [4.1 Regression] ACATS cdd2a02 fails " pinskia at gcc dot gnu dot org
2005-10-22 21:51 ` pinskia at gcc dot gnu dot org
2005-10-30 23:31 ` pinskia at gcc dot gnu dot org
2005-11-22 10:25 ` [Bug ada/18819] [4.1/4.2 " ebotcazou at gcc dot gnu dot org
2005-12-15 13:30 ` ebotcazou at gcc dot gnu dot org
2005-12-15 13:34 ` [Bug ada/18819] [4.2 " ebotcazou at gcc dot gnu dot org
2006-01-17 19:02 ` [Bug ada/18819] [4.1/4.2 Regression] ACATS cdd2a01 cdd2a02 fail " laurent at guerby dot net
2006-01-20 18:39 ` uweigand at gcc dot gnu dot org
2006-01-21 9:32 ` laurent at guerby dot net [this message]
2006-01-22 10:19 ` ebotcazou at gcc dot gnu dot org
2006-01-22 11:43 ` ebotcazou at gcc dot gnu dot org
2006-01-22 11:44 ` ebotcazou at gcc dot gnu dot org
2006-01-22 16:31 ` ebotcazou at gcc dot gnu dot org
2006-01-22 22:29 ` ebotcazou at gcc dot gnu dot org
2006-01-23 15:12 ` charlet at adacore dot com
2006-01-23 15:15 ` ebotcazou at gcc dot gnu dot org
2006-01-25 14:07 ` ebotcazou at gcc dot gnu dot org
2006-01-25 14:08 ` [Bug ada/18819] [4.2 " ebotcazou at gcc dot gnu dot org
2006-01-25 18:03 ` uweigand at gcc dot gnu dot org
2006-02-15 9:40 ` charlet at gcc dot gnu dot org
2006-02-15 10:09 ` [Bug ada/18819] [4.2 Regression] ACATS " ebotcazou at gcc dot gnu dot org
2006-02-15 10:23 ` ebotcazou at gcc dot gnu dot org
2006-02-15 12:57 ` kenner at vlsi1 dot ultra dot nyu dot edu
2006-02-15 17:12 ` ebotcazou at gcc dot gnu dot org
2006-02-15 17:14 ` kenner at vlsi1 dot ultra dot nyu dot edu
2006-03-07 18:33 ` ebotcazou at gcc dot gnu dot org
2006-10-29 23:19 ` [Bug ada/18819] [4.2/4.3 regression] " ebotcazou at gcc dot gnu dot org
2007-02-20 13:12 ` christian dot joensson at gmail dot com
2007-02-20 13:14 ` ebotcazou at gcc dot gnu dot org
2007-02-21 22:59 ` ebotcazou at gcc dot gnu dot org
2007-02-21 23:00 ` ebotcazou at gcc dot gnu dot org
2007-02-21 23:04 ` 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=20060121093213.18173.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).