From: Mark Mitchell <mark@codesourcery.com>
To: dan@cgsoftware.com
Cc: wilson@cygnus.com, schwab@suse.de, gcc@gcc.gnu.org
Subject: Re: Bootstrap failure of gcc-ss-20010409 in ia64
Date: Wed, 11 Apr 2001 18:34:00 -0000 [thread overview]
Message-ID: <20010411183411J.mitchell@codesourcery.com> (raw)
In-Reply-To: <m2bsq2dhzv.fsf@dynamic-addr-83-177.resnet.rochester.edu>
Thanks for the analysis.
It's certainly the case that we now try to output an inlined instance
of a function without having first shown the back end the un-inlined
instance. In my opinion, that's a good thing -- there's no need for
it to know about anything except what we want it to know about.
However, the debug-generation routines need to be able to cope with
that. If you can reproduce Jim's problem, maybe you could help him
with the solution? I've asked him privately to look into it as
quickly as possible -- as a favor to me, the bug-causer -- since it
does apparently affect GCC 3.0 bootstraps on some targets. If you
were willing to help, that would be great.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2001-04-11 18:34 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 6:56 Andreas Schwab
2001-04-11 12:47 ` Jim Wilson
2001-04-11 17:31 ` Mark Mitchell
2001-04-11 17:43 ` Mark Mitchell
2001-04-11 18:28 ` Daniel Berlin
2001-04-11 18:34 ` Mark Mitchell [this message]
2001-04-11 20:24 ` Daniel Berlin
2001-04-11 21:19 ` Mark Mitchell
2001-04-11 21:36 ` Daniel Berlin
2001-04-12 12:27 ` Bill Nottingham
2001-04-12 15:03 ` Daniel Berlin
2001-04-12 21:07 ` Bill Nottingham
2001-04-12 21:46 ` Daniel Berlin
2001-04-12 13:04 ` Jim Wilson
2001-04-12 15:06 ` Daniel Berlin
2001-04-13 8:49 ` Andreas Schwab
2001-04-13 10:04 ` Daniel Berlin
2001-04-13 10:23 ` Andreas Schwab
2001-04-13 12:20 ` Daniel Berlin
2001-04-13 12:39 ` Andreas Schwab
2001-04-13 12:56 ` Daniel Berlin
2001-04-13 13:06 ` Andreas Schwab
2001-04-13 19:13 ` Jim Wilson
2001-04-13 19:59 ` Jim Wilson
2001-04-14 2:01 ` Jim Wilson
2001-04-14 4:08 ` Sam TH
2001-04-14 8:27 ` cvs (was: Bootstrap failure of gcc-ss-20010409 in ia64) Fergus Henderson
2001-04-14 11:28 ` Sam TH
2001-04-14 22:20 ` Jim Wilson
2001-04-14 23:48 ` Russ Allbery
2001-04-16 15:39 ` Bootstrap failure of gcc-ss-20010409 in ia64 Jim Wilson
2001-04-16 17:22 ` Mark Mitchell
2001-04-16 17:45 ` Jim Wilson
2001-04-17 8:22 ` Mark Mitchell
2001-04-17 8:57 ` Daniel Berlin
2001-04-17 11:01 ` Jim Wilson
2001-04-17 15:38 ` Mark Mitchell
2001-04-17 16:16 ` Daniel Berlin
2001-04-17 16:36 ` Mark Mitchell
2001-04-18 14:35 ` debugging optimized programs (Was: Re: Bootstrap failure of gcc-ss-20010409 in ia64) Joern Rennecke
2001-04-18 15:12 ` Daniel Berlin
2001-04-18 15:49 ` Joern Rennecke
2001-04-18 17:06 ` Daniel Berlin
2001-04-18 17:18 ` Daniel Berlin
2001-04-18 12:41 ` Bootstrap failure of gcc-ss-20010409 in ia64 Jim Wilson
2001-04-18 13:49 ` Mark Mitchell
2001-04-18 14:34 ` Jim Wilson
2001-04-18 15:31 ` Mark Mitchell
2001-04-17 18:12 Mike Stump
2001-04-17 19:01 ` Joe Buck
2001-04-17 20:38 ` Daniel Berlin
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=20010411183411J.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=dan@cgsoftware.com \
--cc=gcc@gcc.gnu.org \
--cc=schwab@suse.de \
--cc=wilson@cygnus.com \
/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).