public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/37296] [4.4 Regression] Bootstrap failure compiling libgcc
Date: Thu, 04 Sep 2008 19:31:00 -0000 [thread overview]
Message-ID: <20080904193029.25350.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37296-10110@http.gcc.gnu.org/bugzilla/>
------- Comment #32 from ebotcazou at gcc dot gnu dot org 2008-09-04 19:30 -------
> I tried i586-linux with ira-merge branch. It built libgcc fine.
> So the problem is either fixed on ira-merge branch or it isn't
> caused by IRA merge.
Or isn't exposed on that branch.
It's a stack slot reuse problem during RA compiling df-scan.c. Since it's not
related to this PR, I'm closing it and I'll open a new one.
--
ebotcazou at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37296
next prev parent reply other threads:[~2008-09-04 19:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 4:56 [Bug target/37296] New: Bootstrap failure due to __muldi3 kargl at gcc dot gnu dot org
2008-08-31 4:57 ` [Bug target/37296] " kargl at gcc dot gnu dot org
2008-08-31 6:43 ` [Bug rtl-optimization/37296] " ebotcazou at gcc dot gnu dot org
2008-08-31 12:47 ` gerald at pfeifer dot com
2008-08-31 17:13 ` ebotcazou at gcc dot gnu dot org
2008-08-31 18:41 ` kargl at gcc dot gnu dot org
2008-09-01 3:26 ` vmakarov at redhat dot com
2008-09-01 3:32 ` kargl at gcc dot gnu dot org
2008-09-01 3:33 ` kargl at gcc dot gnu dot org
2008-09-01 5:12 ` kargl at gcc dot gnu dot org
2008-09-01 5:19 ` kargl at gcc dot gnu dot org
2008-09-01 10:30 ` Graham Stott
2008-09-01 10:31 ` graham dot stott at btinternet dot com
2008-09-01 13:01 ` ebotcazou at gcc dot gnu dot org
2008-09-01 13:04 ` ebotcazou at gcc dot gnu dot org
2008-09-01 13:04 ` ebotcazou at gcc dot gnu dot org
2008-09-01 13:18 ` [Bug rtl-optimization/37296] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-09-01 13:41 ` [Bug rtl-optimization/37296] [4.4 Regression] Bootstrap failure compiling libgcc ebotcazou at gcc dot gnu dot org
2008-09-01 13:44 ` rguenth at gcc dot gnu dot org
2008-09-01 16:58 ` sgk at troutmask dot apl dot washington dot edu
2008-09-01 21:47 ` ebotcazou at gcc dot gnu dot org
2008-09-02 10:18 ` ebotcazou at gcc dot gnu dot org
2008-09-02 13:28 ` ebotcazou at gcc dot gnu dot org
2008-09-02 17:30 ` vmakarov at redhat dot com
2008-09-02 17:36 ` ebotcazou at gcc dot gnu dot org
2008-09-02 18:14 ` vmakarov at redhat dot com
2008-09-03 0:29 ` hjl dot tools at gmail dot com
2008-09-03 0:43 ` pinskia at gcc dot gnu dot org
2008-09-03 5:23 ` dominiq at lps dot ens dot fr
2008-09-03 7:57 ` tbm at cyrius dot com
2008-09-03 15:38 ` vmakarov at redhat dot com
2008-09-03 19:52 ` vmakarov at gcc dot gnu dot org
2008-09-03 21:07 ` ebotcazou at gcc dot gnu dot org
2008-09-04 5:54 ` hjl dot tools at gmail dot com
2008-09-04 6:17 ` sgk at troutmask dot apl dot washington dot edu
2008-09-04 13:09 ` hjl dot tools at gmail dot com
2008-09-04 14:55 ` hjl dot tools at gmail dot com
2008-09-04 19:31 ` ebotcazou at gcc dot gnu dot org [this message]
2008-11-13 16:01 ` jakub 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=20080904193029.25350.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).