Additional peephole pass(es)

Stefan Franke stefan@franke.ms
Mon Apr 20 10:20:35 GMT 2020


Hi there,

 

is there a chance that a patch would be accepted if it adds (an) additional
peephole pass(es)?

 

I'm not content with the capabilities of the combine pass and a convenient
way would be to insert an additional pass in front/after the combine pass.
It's way easier to maintain than the spaghetti code in combine and ss long
there is nothing defined in the cpu's md file, the pass gets skipped, so the
overhead for non-users is almost non existent.

 

Right now I'm applying the same set as in the final peephole run, but I
would add a separate keyword per pass, e.g. peephole_precombine, etc. p.p.

 

Your thoughts?

 

/cheers Stefan

 




More information about the Gcc-help mailing list