From: Daniel Jacobowitz <drow@false.org>
To: Jim Wilson <wilson@specifixinc.com>, gcc-patches@gcc.gnu.org
Subject: Reusing stack slots
Date: Sun, 04 Jul 2004 03:12:00 -0000 [thread overview]
Message-ID: <20040704031148.GA21600@nevyn.them.org> (raw)
In-Reply-To: <40E1B214.7030106@specifixinc.com>
On Tue, Jun 29, 2004 at 11:16:52AM -0700, Jim Wilson wrote:
> Ian Lance Taylor wrote:
> >For example, here is a quickie test for whether arrays declared in
> >different blocks overlap. This test appears to currently always fail.
>
> See bug #9997 which has a 4 line patch (only two lines of actual code)
> that fixes this. It just needs someone to test the patch. This is in
> my backlog of stuff to look at some day, but it is probably faster if
> someone else does it.
I retested this patch. As you suspected, it no longer causes a
regression. However, I can't identify the previously problematic
code in alias2.C; tree-ssa generates drastically different code.
The patch no longer affects the code generated for that test.
However, the patch no longer fixes the testcase for PR 9997. Something
else has broken it since then - preserve_temp_slots is no longer called
with anything but NULL_RTX. One of the other related problems you've
mentioned is probably to blame.
--
Daniel Jacobowitz
next parent reply other threads:[~2004-07-04 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13588461-C746-11D8-9F4A-003065BDF310@apple.com>
[not found] ` <87eko26vjr.fsf@taltos.codesourcery.com>
[not found] ` <40DDBF80.9070108@codesourcery.com>
[not found] ` <87659e6slj.fsf@taltos.codesourcery.com>
[not found] ` <40DDD078.20308@codesourcery.com>
[not found] ` <87eko062ls.fsf@taltos.codesourcery.com>
[not found] ` <m3659bfqi2.fsf@gossamer.airs.com>
[not found] ` <40E1B214.7030106@specifixinc.com>
2004-07-04 3:12 ` Daniel Jacobowitz [this message]
2004-07-08 3:32 ` Jim Wilson
2004-07-08 3:39 ` Zack Weinberg
2004-07-08 4:38 ` Richard Henderson
2004-07-08 19:22 ` Joern Rennecke
2004-07-08 20:18 ` Richard Henderson
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=20040704031148.GA21600@nevyn.them.org \
--to=drow@false.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=wilson@specifixinc.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).