From: Mark Mitchell <mark@codesourcery.com>
To: wilson@cygnus.com
Cc: gcc@gcc.gnu.org
Subject: Re: Bootstrap failure of gcc-ss-20010409 in ia64
Date: Wed, 18 Apr 2001 13:49:00 -0000 [thread overview]
Message-ID: <20010418134948I.mitchell@codesourcery.com> (raw)
In-Reply-To: <200104181941.MAA15831@wilson.cygnus.com>
>>>>> "Jim" == Jim Wilson <wilson@cygnus.com> writes:
Jim> This particular problem with the debug info did not exist
Jim> until you checked in a patch that turned off the RTL inliner.
Jim> As such, it represents a regression, and regressions should
Jim> be fixed.
That's fair.
Jim> I see this as another part of the tree inliner that isn't
Jim> finished yet. The RTL inliner handled this correctly. It is
Jim> easy for the tree inliner to handle this correctly too, we
Jim> just haven't written the code for it yet. This should be
Jim> done before the tree inliner permanently replaces the RTL
Jim> inliner.
I guess I'm still not sure exactly what needs to be done. Is all that
needs to be done:
If the function for which we are about to generate code is
inline, then:
- Copy the BLOCK tree.
- Generate code.
- Restore the original BLOCK tree, throwing away the copy.
?
If so, you're correct that that isn't a particularly difficult task.
I can certainly code that up, given a test-case, and such.
I don't know if it's really that simple, or not.
Jim> they don't interfere with bootstraps. However, debug info
Jim> support is important for maintaining gcc and other programs,
Jim> and a lot of people have put a lot of hard work into making
Jim> the debug info useful. We should not lightly abandon that
Jim> effort.
I agree completely.
Jim> large C++ EH/Unwind API patch. The only testcase we have for
Jim> this problem fails because of fake variables inserted by the
Jim> C++ front end for EH purposes. It is unclear if this bug
Jim> will be triggered by any other testcases.
Interesting point. It is likely that it could be -- the front-end
doesn't really do anything special with those variables -- but your
point that we don't know how often the bug will come up is
interesting.
Jim> problem today. I will check in a patch to punt on the
Jim> branch, and then document the correct fix in dwarf2out.c on
Jim> the trunk, or if it isn't too hard, I may just write the damn
Jim> code myself.
Thank you, for the analysis, the commentary, and the fix.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2001-04-18 13:49 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
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 [this message]
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=20010418134948I.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--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).