sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: brendan@cygnus.com
To: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu>
Cc: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: sam on DEC OSF/1 Alpha?
Date: Mon, 15 Feb 1993 20:26:07 -0500	[thread overview]
Message-ID: <9302160126.AA15916@cygnus.com> (raw)
In-Reply-To: Your message of "Mon, 15 Feb 93 19:33:44 EST." <93Feb15.193359est.2763@hawkwind.utcs.toronto.edu>

>  Well, thanks to John Mackin, I now have the problem identified.
> Pointers in DEC Alpha OSF/1 are 64 bits (as is 'long'), and the sam to
> samterm protocol passes pointers around, lopped to 32 bits. Naturally
> this causes problems when samterm gets a lopped pointer back and
> attempts to use it.
> 
>  Unfortunately, I'm not quite sure of the best way to fix this.
> Time to go spelunkering the sources.

One of the best ways to handle this that I've found is to prototype
all of the functions, then find where integers are being passed as
pointers, and visa-versa.  (ptrs are 64 bits, ints are 32...if you
pass `0' where a pointer is expected, it'll be bogus) Then when you
compile with an ANSIish compiler (use gcc :) ), it'll tell you about
all of the violations.

Brendan

--
Brendan Kehoe                                               brendan@cygnus.com
Cygnus Support, Mountain View, CA                              +1 415 903 1400
                     ``In a cruel and imperfect world,'' says critic Rex Reed,
 ``[Audrey Hepburn] was living proof that God could still create perfection.''


  reply	other threads:[~1993-02-16  1:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-02-16  0:33 Chris Siebenmann
1993-02-16  1:26 ` brendan [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-02-16  3:01 Chris Siebenmann
1993-02-15 16:28 Chris Siebenmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9302160126.AA15916@cygnus.com \
    --to=brendan@cygnus.com \
    --cc=cks@hawkwind.utcs.toronto.edu \
    --cc=sam-fans@hawkwind.utcs.toronto.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).