home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.ultrix:8842 comp.unix.wizards:5205
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!olivea!charnel!sifon!thunder.mcrcim.mcgill.edu!mouse
- From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
- Newsgroups: comp.unix.ultrix,comp.unix.wizards
- Subject: Re: malloc on ultrix
- Message-ID: <1992Dec12.232417.1526@thunder.mcrcim.mcgill.edu>
- Date: 12 Dec 92 23:24:17 GMT
- References: <Byys01.6qs@ansoft.com> <1992Dec9.142830.706@aosg.gsf.dec.com>
- Distribution: na
- Organization: McGill Research Centre for Intelligent Machines
- Lines: 27
-
- > Distribution: usa
-
- Someone is leaking USA distribution out of the US....
-
- In article <1992Dec9.142830.706@aosg.gsf.dec.com>, gaf@alpha.aosg.gsf.dec.com (Gerald Feldman) writes:
- > In article <Byys01.6qs@ansoft.com>, elliot@truth.ansoft.com (mike elliot) writes:
-
- >> I am writing a memory allocator for my application, and under Ultrix
- >> I get a bunch of `Fixed up unaligned data access' messages.
- > Ultrix per se. does not require any data alignment.
-
- Aren't there some things that must be on page boundaries?
-
- > However, if you are using Ultrix on a DECStation (not a VAX), then
- > you need to align on a longword boundary. While this does not
- > necessary apply to your application, malloc() must return a pointer
- > to memory that is properly aligned. You need to provide more data on
- > the fixup messages. I am assuming that these are from ld.
-
- More likely, I'd say, from the kernel at run-time, as the kernel
- notices an unaligned access trap and chooses to handle it by simulating
- the unaligned reference.
-
- der Mouse
-
- mouse@larry.mcrcim.mcgill.edu
-