> On 24 Mar 2016, at 16:35, Cary Coutant wrote:
>
> It's fine to have different regions of code with different register
> save states, but it's a bad idea to have two paths join without
> compensation code at the end of one or both paths to match the states.
> For example, you could restore the
>
> On 19 Mar 2016, at 12:46, Jonas H. wrote:
>
> I’m working on a edu/research compiler that has yet to be equipped with DWARF
> info. Unlike GCC/Clang/… it doesn’t have spill slots that are “constant”
> within a procedure, i.e. may procedure code like this:
>
> …
>
> Is this supported by
