On 03.12.2018 21:25, Alexander Popov wrote:
> But I think it's better to register the 'stackleak_cleanup' pass just one pass
> earlier -- before the '*free_cfg' pass. I'll double check it for different
> versions of gcc on all supported architectures and return with a new patch.
I've tested this i
the 'reload' pass. That allows gcc to do some weird optimization in
>>> function prologues and epilogues, which are generated later [1].
>>>
>>> Let's avoid that by registering the 'stackleak_cleanup' pass before
>>> the 'mach'
David Given wrote:
[...]
> When I actually try to build stuff, however, the branch gets emitted but
> then silently deleted during the mach pass.
Solved: turned out to be old code in the TARGET_MACHINE_DEPENDENT_REORG,
dating from the port I was basing my backend on, which was mangling my
c
tecture is utterly traditional and the code above is stolen
pretty much intact from the moxie port (which I'm using as a reference
because it seems to be simple and easy to understand).
When I actually try to build stuff, however, the branch gets emitted but
then silently deleted during the m
On 11/05/10 09:01, Ian Lance Taylor wrote:
Abdul Wahid Memon writes:
Can anyone please give me a two line description about mach pass in
GCC or any source reference for that.
I don't know what you mean by "mach pass".
I'd hazard a guess Abdul is referring to the mac
Abdul Wahid Memon writes:
> Can anyone please give me a two line description about mach pass in
> GCC or any source reference for that.
I don't know what you mean by "mach pass".
Ian
Hello all
Can anyone please give me a two line description about mach pass in
GCC or any source reference for that.
Regards
Abdul
