public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rolf dot ebert dot gcc at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/31108] [4.2 regression] ACATS C35507M fails Date: Sun, 11 Mar 2007 22:17:00 -0000 [thread overview] Message-ID: <20070311221745.4257.qmail@sourceware.org> (raw) In-Reply-To: <bug-31108-8123@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rolf dot ebert dot gcc at gmx dot de 2007-03-11 22:17 ------- I have to rerun the ACATS tests with more disk space available. After the C3 tests all other failures were due to "disk full". Currently c35507m is the only failure in 4.2 on MinGW that I know of. But as I said, I did not yet run the complete test suite. Had the fix for PR 26797 been back-ported to the 4.2 branch? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31108
next prev parent reply other threads:[~2007-03-11 22:17 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-09 15:37 [Bug ada/31108] New: [regression 4.2] ACATS C35507M fails on MinGW rolf dot ebert dot gcc at gmx dot de 2007-03-10 16:57 ` [Bug ada/31108] [4.2 regression] ACATS C35507M fails ebotcazou at gcc dot gnu dot org 2007-03-11 22:17 ` rolf dot ebert dot gcc at gmx dot de [this message] 2007-03-17 7:33 ` ebotcazou at gcc dot gnu dot org 2007-03-22 13:08 ` rolf dot ebert dot gcc at gmx dot de 2007-03-22 13:31 ` ebotcazou at gcc dot gnu dot org 2007-03-22 13:32 ` ebotcazou at gcc dot gnu dot org 2007-09-26 19:11 ` pinskia at gcc dot gnu dot org 2007-09-26 19:11 ` pinskia at gcc dot gnu dot org 2007-09-28 3:50 ` mmitchel at gcc dot gnu dot org 2007-10-09 19:30 ` mmitchel at gcc dot gnu dot org 2008-02-01 16:58 ` jsm28 at gcc dot gnu dot org 2008-03-16 17:18 ` rguenth at gcc dot gnu dot org 2008-05-19 20:47 ` jsm28 at gcc dot gnu dot org 2008-09-20 14:01 ` 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=20070311221745.4257.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: 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).