From: Stan Sieler <sieler@allegro.com>
To: jcurry@cup.hp.com (John Curry)
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Some PA-RISC 2.0 Gotchas
Date: Fri, 11 Feb 2000 09:52:43 -0800 (PST) [thread overview]
Message-ID: <200002111752.JAA01509@opus.allegro.com> (raw)
In-Reply-To: <00ec01bf74b2$f4c6c050$1c80100f@jc356611.cup.hp.com> from "John Curry" at Feb 11, 2000 09:10:54 AM
Re:
> - In 2.0, function pointers are not addresses to functions, but are
> addresses to data strcutures
> called "function descriptors". So, if assembly code gets passed a pointer to
> a function, it will have
> to remember which slot in the "function descriptor" the actual function
> pointer resides.
They're pointers to data on HP-UX 10.20 as well.
> - There are some places in the kernel where the implicit assumption that
> longs == ints will break!
:)
My pet peeve...
Code should almost *never* use "short", "int", or "long" ...
but instead, "int32" and "int64" (or whatever) should be used.
I've lost track of the number of bugs I've seen caused by this.
(Ok, one exception...if you're calling a system function documented as
using "int" or "long", then you can declare variables of those type
... but be very careful using them, and file a bug report with the vendor :)
--
Stan Sieler sieler@allegro.com
www.allegro.com/sieler/wanted/index.html www.allegro.com/sieler
next prev parent reply other threads:[~2000-02-11 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-11 17:10 [parisc-linux] Some PA-RISC 2.0 Gotchas John Curry
2000-02-11 17:52 ` Stan Sieler [this message]
2000-02-11 18:21 ` Philipp Rumpf
-- strict thread matches above, loose matches on Subject: below --
2000-02-11 18:38 Christopher Neufeld
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=200002111752.JAA01509@opus.allegro.com \
--to=sieler@allegro.com \
--cc=jcurry@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.