public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schlie at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19920] [4.0 Regression] build broken on several targets due to recent 'DC' type update to libgcc2
Date: Tue, 15 Feb 2005 00:54:00 -0000 [thread overview]
Message-ID: <20050214203223.24695.qmail@sourceware.org> (raw)
In-Reply-To: <20050212040652.19920.schlie@comcast.net>
------- Additional Comments From schlie at comcast dot net 2005-02-14 20:32 -------
(In reply to comment #9)
> None of the primary/secondary targets are known to fail so removing the target milestone.
Although I understand none of the failures are on primary/secondary targets, might someone who is
most familiar with, and intends to hopefully maintain libgcc2 have a chance to look at this, in hopes it
may be remedied relatively easily in a way consistent with their longer term plans?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19920
next prev parent reply other threads:[~2005-02-14 20:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 16:29 [Bug c/19920] New: avr target build broken by " schlie at comcast dot net
2005-02-12 16:32 ` [Bug target/19920] " pinskia at gcc dot gnu dot org
2005-02-12 16:37 ` schlie at comcast dot net
2005-02-12 16:46 ` bjoern dot m dot haase at web dot de
2005-02-12 19:28 ` [Bug target/19920] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-02-12 22:32 ` bjoern dot m dot haase at web dot de
2005-02-12 22:35 ` bjoern dot m dot haase at web dot de
2005-02-13 16:44 ` schlie at comcast dot net
2005-02-14 15:52 ` corsepiu at gcc dot gnu dot org
2005-02-14 15:56 ` steven at gcc dot gnu dot org
2005-02-14 15:59 ` [Bug target/19920] [4.0 Regression] build broken on several targets due to " steven at gcc dot gnu dot org
2005-02-14 17:51 ` corsepiu at gcc dot gnu dot org
2005-02-14 19:53 ` [Bug middle-end/19920] " pinskia at gcc dot gnu dot org
2005-02-15 0:54 ` schlie at comcast dot net [this message]
2005-02-15 5:32 ` bjoern dot m dot haase at web dot de
2005-02-15 23:24 ` pinskia at gcc dot gnu dot org
2005-02-16 6:27 ` bjoern dot m dot haase at web dot de
2005-02-16 15:30 ` corsepiu at gcc dot gnu dot org
2005-02-16 16:30 ` schlie at comcast dot net
2005-02-16 19:14 ` corsepiu at gcc dot gnu dot org
2005-02-16 19:45 ` schlie at comcast dot net
2005-02-17 9:42 ` rth at gcc dot gnu dot org
2005-02-17 10:00 ` cvs-commit at gcc dot gnu dot org
2005-02-17 22:47 ` rth at gcc dot gnu dot org
2005-04-20 2:25 ` pinskia 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=20050214203223.24695.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).