* Stack-based pseudos
@ 2003-03-07 20:23 tm_gccmail
0 siblings, 0 replies; only message in thread
From: tm_gccmail @ 2003-03-07 20:23 UTC (permalink / raw)
To: joern.rennecke, vmakarov; +Cc: gcc, kkojima, matz, naveens
I was thinking about stack-based pseudos in stack-reorg.c last night, and
realized they might be useful for solving other problems as well.
The previous problem I reported with function prologue/epilogue
scheduling:
http://gcc.gnu.org/ml/gcc-bugs/2003-02/msg01290.html
http://gcc.gnu.org/ml/gcc-bugs/2003-02/msg01322.html
...might be solvable by having a new barrier type which prevents movement
of stack-based pseudos across the barrier.
In addition, it seems applicable to;
http://gcc.gnu.org/ml/gcc-bugs/2003-03/msg00004.html
...to improve alias analysis on stack-based arrays.
Am I expecting too much, or are these solvable with stack-based pseudos?
Toshi
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-03-07 19:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-07 20:23 Stack-based pseudos tm_gccmail
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).