This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/66790] Invalid uninitialized register handling in REE
- From: "derodat at adacore dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 12 Oct 2015 14:47:50 +0000
- Subject: [Bug rtl-optimization/66790] Invalid uninitialized register handling in REE
- Auto-submitted: auto-generated
- References: <bug-66790-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66790
--- Comment #43 from Pierre-Marie de Rodat <derodat at adacore dot com> ---
(In reply to Bernd Schmidt from comment #42)
> I don't think that would actually help. Even if something is an actual
> incoming argument register, it may still be uninitialized by the caller.
Sure, but my understanding is that what matters in DF is what happens inside
the function, so we can assume arguments are always initialized.
Actually this makes sense in the context of REE as well: we have one
(artificial) def for arguments so since this def has no corresponding
instruction, REE will not be able to remove z-extensions reaching this def.
That being said, I failed to get the âis it really used for incoming argumentsâ
hard-reg predicate, so falling back to your proposal: I will followup on
gcc-patches@.
Thanks! :-)