Soheil Shahrouz

Thank you for opening this issue. It seems that some move generators call pick_from_block() function to select a block randomly. This function has a while loop that tries to find...

I merged master to this branch to see if the labeler trigger changes from pull_request to pull_request_target. It did! Hopefully triage job does not fail this time.

Superseded by #2526.

> @soheilshahrouz can you take a look at this one when it is ready? I can review it over the weekend.

@w0lek Is this PR ready for review or you have more commits to push?

@vaughnbetz I applied your comments. Here is [the link](https://docs.google.com/spreadsheets/d/1vKspFxHDAFFv-80apVzBddpAIP62kzOODyjQ20IS_8U/edit?usp=sharing) to QoR for Titan that shows the new interface for specifying availale move types does not degraged the runtime.

You should use --enable_analytic_placer command line option. Run vpr with -h option and see the help information for this option. https://github.com/verilog-to-routing/vtr-verilog-to-routing/blob/c9fcf98dd880be1f996281ae42805936b17acf4f/vpr/src/base/read_options.cpp#L2026-L2031

Closing due to lack of activity.

[Link](https://docs.google.com/spreadsheets/d/1sUdy0iZMlNW_n4mnRfk0pMV9mrPGps_kbiE7WAAsELw/edit?usp=sharing) to QoR results for Titan benchmarks. They are the same as master.

@vaughnbetz I applied your comments. Ready for review.