public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/22274] [4.1 Regression] string[1-4].m, const-str-5.m fails with the gnu runtime
Date: Tue, 05 Jul 2005 00:40:00 -0000 [thread overview]
Message-ID: <20050705004014.17484.qmail@sourceware.org> (raw)
In-Reply-To: <20050702040424.22274.pinskia@gcc.gnu.org>
------- Additional Comments From hp at gcc dot gnu dot org 2005-07-05 00:40 -------
I was about to enter a separate report, but it seems the bug is the same as this
one, so I just add the following as a comment. A few more failures than the
original report; I don't know what to make of that.
Last known to work on: "Wed Jun 29 13:20:13 UTC 2005".
With LAST_UPDATED: "Wed Jun 29 21:40:22 UTC 2005" up til
and including "Mon Jul 4 10:24:52 UTC 2005" I get these
objc failures:
objc.dg/const-str-5.m (test for excess errors)
objc/execute/string1.m compilation, -O0
objc/execute/string1.m compilation, -O1
objc/execute/string1.m compilation, -O2
objc/execute/string1.m compilation, -O3 -fomit-frame-pointer
objc/execute/string1.m compilation, -O3 -g
objc/execute/string1.m compilation, -Os
objc/execute/string2.m compilation, -O0
objc/execute/string2.m compilation, -O1
objc/execute/string2.m compilation, -O2
objc/execute/string2.m compilation, -O3 -fomit-frame-pointer
objc/execute/string2.m compilation, -O3 -g
objc/execute/string2.m compilation, -Os
objc/execute/string3.m compilation, -O0
objc/execute/string3.m compilation, -O1
objc/execute/string3.m compilation, -O2
objc/execute/string3.m compilation, -O3 -fomit-frame-pointer
objc/execute/string3.m compilation, -O3 -g
objc/execute/string3.m compilation, -Os
objc/execute/string4.m compilation, -O0
objc/execute/string4.m compilation, -O1
objc/execute/string4.m compilation, -O2
objc/execute/string4.m compilation, -O3 -fomit-frame-pointer
objc/execute/string4.m compilation, -O3 -g
objc/execute/string4.m compilation, -Os
With the message in the .log being similar for all:
x/gcc/testsuite/objc/execute/string1.m:17: internal compiler error: tree check:
expected identifier_node, have type_decl in generate_strings, at
objc/objc-act.c:2445
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |hp at gcc dot gnu dot org
Last reconfirmed|2005-07-02 04:05:40 |2005-07-05 00:40:13
date| |
Summary|[4.1 Regression] |[4.1 Regression] string[1-
|string[12].m fails with the |4].m, const-str-5.m fails
|gnu runtime |with the gnu runtime
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22274
next prev parent reply other threads:[~2005-07-05 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 4:04 [Bug objc/22274] New: [4.1 Regression] string[12].m " pinskia at gcc dot gnu dot org
2005-07-02 4:05 ` [Bug objc/22274] " pinskia at gcc dot gnu dot org
2005-07-02 4:06 ` pinskia at gcc dot gnu dot org
2005-07-05 0:40 ` hp at gcc dot gnu dot org [this message]
2005-07-06 21:11 ` [Bug objc/22274] [4.1 Regression] string[1-4].m, const-str-5.m " zlaski at apple dot com
2005-07-07 6:26 ` cvs-commit at gcc dot gnu dot org
2005-07-07 6:33 ` zlaski at apple dot com
2005-07-07 21:43 ` cvs-commit 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=20050705004014.17484.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).