From: Nial Stewart on
> Quartus is worse than Maxplus-2 for the crashes per day.


0.0000002 rather than 0.00000015 ?

:-)


> It also doesn't produce the same resulting fuse map for the
> same input file. This means that you can't recompile your old
> code to make the same compiled results.

AFAIR it _should_ give repeatable results with the same input
files and constraints (might be wrong here).



Nial


From: MooseFET on
On Feb 11, 3:06 am, "Nial Stewart"
<nial*REMOVE_TH...(a)nialstewartdevelopments.co.uk> wrote:
> > Quartus is worse than Maxplus-2 for the crashes per day.
>
> 0.0000002 rather than 0.00000015 ?
>
> :-)
More like 0.2 vs 0.3

>
> > It also doesn't produce the same resulting fuse map for the
> > same input file. This means that you can't recompile your old
> > code to make the same compiled results.
>
> AFAIR it _should_ give repeatable results with the same input
> files and constraints (might be wrong here).

It doesn't seem to make the same choices about internal parts.
I have to support some very old designs.

>
> Nial

From: krw on
On Thu, 11 Feb 2010 11:06:13 -0000, "Nial Stewart"
<nial*REMOVE_THIS*@nialstewartdevelopments.co.uk> wrote:

>> Quartus is worse than Maxplus-2 for the crashes per day.
>
>
>0.0000002 rather than 0.00000015 ?
>
>:-)
>
>
>> It also doesn't produce the same resulting fuse map for the
>> same input file. This means that you can't recompile your old
>> code to make the same compiled results.
>
>AFAIR it _should_ give repeatable results with the same input
>files and constraints (might be wrong here).

I don't know why you would expect two versions of software, much less
two completely different packages, to create exactly the same bit map?
I wouldn't expect two passes of the *same* installation to create
exactly the same design. There is too much magic going on in PAR.
From: krw on
On Thu, 11 Feb 2010 11:04:13 -0000, "Nial Stewart"
<nial*REMOVE_THIS*@nialstewartdevelopments.co.uk> wrote:

>> It hung on me yesterday - the fourth fatal bug in five days of usage. I'm a former CAD programmer
>> also so am both sympathetic and unsympathetic.
>
>
>I think I can probably count on the fingers of one hand the number of
>times it's crashed on me.

O haven't had Quartus-II behave badly on me either, though my current
design isn't pushing anything very hard at all. It's a little tight,
but on a very small device.

>What are you running it on, and do you have enough memory (not usually
>a problem until you get to big devices)?
From: MooseFET on
On Feb 12, 2:12 pm, krw <k...(a)att.bizzzzzzzzzzz> wrote:
> On Thu, 11 Feb 2010 11:06:13 -0000, "Nial Stewart"
>
> <nial*REMOVE_TH...(a)nialstewartdevelopments.co.uk> wrote:
> >> Quartus is worse than Maxplus-2 for the crashes per day.
>
> >0.0000002 rather than 0.00000015 ?
>
> >:-)
>
> >> It also doesn't produce the same resulting fuse map for the
> >> same input file. This means that you can't recompile your old
> >> code to make the same compiled results.
>
> >AFAIR it _should_ give repeatable results with the same input
> >files and constraints (might be wrong here).
>
> I don't know why you would expect two versions of software, much less
> two completely different packages, to create exactly the same bit map?
> I wouldn't expect two passes of the *same* installation to create
> exactly the same design.  There is too much magic going on in PAR.

If the desired operation of the device is fully described by the input
and the fitter gets the optimum fit, I would expect that 2 versions of
the
fitter would most likely make the same results. There is no reason
for
it to make different results.