Re: ISE 10.1 - Initial experience



On Sat, 29 Mar 2008 08:18:23 -0700 (PDT), emeb <ebrombaugh@xxxxxxxxx>
wrote:

I've got a fairly large design that I've been working with in ISE
9.2.04 for a while - it takes about 90% of a V2P100 and runs to
completion in about 3.5 to 4 hours on my Linux x86_64 system (Athlon
dual core 3800 w/ 4GB) using home-made make scripts. I decided to take
10.1 out for a spin to see if it really helps speed things up. Here's
what I've seen on the first few runs:

- XST seems to run about as fast as it used to.
- NGDBUILD seems faster and seems to find errors in timing exceptions
more quickly.
- MAP works about the same.
- PAR takes a lot longer to run. I'm seeing 8 hour runs that used to
take 2 - 2.5 hours in 9.2.04 with the same constraints. It appears to
be coming up with bad placements (Phase 12.27 seems to take _forever_)
that are impossible to route successfully.

I'm in the process of adding more timing exceptions and this seems to
help, but I still haven't had a successful PAR run. Let me re-iterate:
9.2.04 didn't have any trouble with this design using the exact same
source and constraints.

Summary: 10.1 isn't working as well as 9.2.04. I'll probably be
shelving it and waiting for the service pack.



Well, my designs have all compiled OK. A complex design (83% of an
XC3S400, with a microblaze and a whole bunch of proprietary
peripherals included, with minor differences in pinout and contents
over two different boards), has compiled consistently in 20% less time
(25 minutes brought down to 20 minutes), just adding only 7 slices to
the final design. PC, WXP SP2 ES, dual athlon)

The GCC compiler has some differences, as it will migrate some data
from bss to text (which might be a problem for me, as the may be
located on different RAM types, but I have not yet identified the
differences). 4 different SW projects working on both different above
mentioned boards working OK.

So, for me, everything seem to work fine up to this hour. Of course,
the work is being done on a branch, the main development remains on
9.2.4(ISE)2(EDK).

Now, I'd really love receiving my license update to register my
products (EDK and Chipscope), so I may begin working with it....

Best regards,

Zara
.



Relevant Pages

  • Re: why still use C?
    ... OOP in general tends to be slower. ... As if the compiler didn't know... ... > their associated method functions from a design perspective. ... as a language design I feel it has failed. ...
    (comp.lang.c)
  • Re: writeObject signature
    ... > or the compiler must do a cast to Object. ... Java refers to a syntax for type conversion -- namely, ... it would be wrong (or bad design) to ...
    (comp.lang.java.programmer)
  • Re: Inside an FBI Computer Forensics Lab
    ... You should be comparing a hardware engineer who puts ... design done in a hardware description language. ... My compiler is open source also. ... The attack involves compromising the compiler before the hash ...
    (alt.privacy)
  • Re: Another $17.4 Billion WASTED
    ... program from shrouded code is anything but "pathetically simple". ... perhaps with user-selected features and compiler ... uncommented code from a programmer that is using ... the detailed software design document put together by the PHD that ...
    (rec.autos.driving)
  • Re: slightly OT: error handling conventions
    ... - making a well design is more than the half work. ... goto is evil and should be avoided whenever possible ... break them down in nested fuctions increases the readability. ... the compiler knows better than you why it is crying. ...
    (comp.lang.c)