[Info-vax] HP wins Oracle Itanium case

[ChrisQ]

On 08/22/12 20:48, John Wallace wrote:

>
> For the last few days I have been trying to sort an unfortuante
> scenario where embedded compiler A does the right thing but embedded
> compiler B doesn't, and for regulatory reasons life would be (much)
> easier with compiler B.
>
> Today I covered my desktop with five columns of A4. Four columns of
> four sections where compiler A matches compiler B, and one for the one
> where the differences are. Lots of scribbling. Green and white would
> have been good too.

I assume you are comparing asm source outputs ?. I know it's windows,
but have found windiff quite usefull for comparing text files. It's a
free download as well.

As for the code, have you tried rewriting the buggy section in a different
way, or unnest loops, simplify excessive levels of  if/then/else etc ?.
Something i've had to do in the past to work around compiler bugs, though
not for some years.

Post more details. Source code snippet and asm output in both cases.
Enquiring minds and all that :-).

>
> A CDA-like implementation of something like PDF would in principle
> have meant that compatible apps would be able to read a the text from
> a PDF file, by means of some intervening layer whose API was all they
> needed to know, without actually needing to know about PDF itself.
> Gee, would anyone be able to use something like that?
>
> Give it another ten years, maybe CDA will get reinvented and Apple or
> MS will patent it in the US and elsewhere.

I always liked vax decwrite, which I guess depended quite a bit on cda.
Years before open orifice and actually very good.

One of the problems I have with 90's era docs are that many are in
postscript and it would be really, really good to find a simple, lean
and fast postscript viewer...

Regards,

Chris