Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
15 years ago

Can using .qxp as source file reduce compilation time?

Hi,

I would like to know how does using .qxp as source file helps to reduce compilation time in a team-based design environment?

Thanks and cheers!

4 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    I'm pretty sure .qxp as source only supports post-synthesis, i.e. it won't preserve placement and routing. So it certainly will cut down your synthesis time, but wouldn't have any affect on fit time. You'd have to decide if that's worth it. (I think .qxp as source will support placement and routing in the upcoming release. Not positive though.)

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    --- Quote Start ---

    I'm pretty sure .qxp as source only supports post-synthesis, i.e. it won't preserve placement and routing. So it certainly will cut down your synthesis time, but wouldn't have any affect on fit time. You'd have to decide if that's worth it. (I think .qxp as source will support placement and routing in the upcoming release. Not positive though.)

    --- Quote End ---

    Hi Rysc,

    as far as I know it possible to export the routing ( that also means the Placement). You can choose this option in the "Export Design Partition" tab. After import of the partition in the top project you can choose the fitter preservation level between:

    netlist only

    placement

    placement & routing

    Of course you have to define LogicLock regions for your design partitions in order to make

    sure that no placement conflict occurs.

    Kind regards

    GPK
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    You're right. I consider import/export of QXPs, and "QXP as source" to be two different flows, and I was just responding to the latter. For import/export, everything you've said is correct, and probably good that it's clarified.