public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/15100] [3.4/3.5? Regression] cc1plus got hang-up on libstdc++-v3/testsuite/abi_check.cc
Date: Fri, 30 Apr 2004 11:27:00 -0000 [thread overview]
Message-ID: <20040430105847.14643.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040423140349.15100.kkojima@gcc.gnu.org>
------- Additional Comments From kkojima at gcc dot gnu dot org 2004-04-30 10:58 -------
The mainline (20040425 x86-linux cross to sh4-linux) also hangs on .i file
got from 3.4.0 abi_check.cc. Unfortunately, same .i file can't be compiled
on 3.3-branch for another reasons like new __attribute__ expression and I
don't have any appropriate testcase for this PR against 3.3-branch ATM.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15100
next prev parent reply other threads:[~2004-04-30 10:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 14:44 [Bug bootstrap/15100] New: " kkojima at gcc dot gnu dot org
2004-04-23 15:54 ` [Bug optimization/15100] " pinskia at gcc dot gnu dot org
2004-04-30 9:17 ` kkojima at gcc dot gnu dot org
2004-04-30 10:49 ` giovannibajo at libero dot it
2004-04-30 10:58 ` [Bug optimization/15100] [3.4/3.5? Regression] " giovannibajo at libero dot it
2004-04-30 11:27 ` kkojima at gcc dot gnu dot org [this message]
2004-04-30 13:30 ` giovannibajo at libero dot it
2004-04-30 14:06 ` kkojima at gcc dot gnu dot org
2004-05-12 19:31 ` cvs-commit at gcc dot gnu dot org
2004-05-13 0:09 ` [Bug optimization/15100] [3.4 " pinskia at gcc dot gnu dot org
2004-05-18 21:13 ` [Bug rtl-optimization/15100] " cvs-commit at gcc dot gnu dot org
2004-05-18 21:20 ` kkojima 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=20040430105847.14643.qmail@sources.redhat.com \
--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).