On Tue, 30 Jun 2009 20:21:03 +0200 (CEST), Alexander Best
alexbes...@math.uni-muenster.de wrote:
thanks. now the output gets redirected using . i'm quite new to programming
under unix. sorry for the inconvenience.
so i guess there is no really easy way to output an inhomogeneous struct to
On Wed, 01 Jul 2009 00:06:05 +0200 (CEST), Alexander Best
alexbes...@math.uni-muenster.de wrote:
thanks for all the help. i decided to take the pill and coded all the
fprintfs by hand. here's the result. usually i'd stick to a higher
level languag, but i need C's inline assembly support:
2009/7/4 Giorgos Keramidas keram...@ceid.upatras.gr:
[snip]
s/0x%/%#.2hh/g
--
Igor
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
Status update:
http://gcc.gnu.org/ml/gcc-patches/2009-07/msg00102.html
I replied to the last email in the thread but haven't
heard back yet. Presumably I'll be maintaining the FreeBSD
x86_64 port.
I'm about to start work on the FreeBSD port now.
___
i'm wondering why mmap and munmap behave differently when it comes to a length
argument of zero. allocating memory with mmap for a zero length file returns a
valid pointer to the mapped region.
munmap however isn't able to remove a mapping with no length.
wouldn't it be better to either forbid
On 7/4/09, Alexander Best alexbes...@math.uni-muenster.de wrote:
i'm wondering why mmap and munmap behave differently when it comes to a
length
argument of zero. allocating memory with mmap for a zero length file returns
a
valid pointer to the mapped region.
there is V flag for malloc.conf
On Sun, 5 Jul 2009, Alexander Best wrote:
i'm wondering why mmap and munmap behave differently when it comes to a length
argument of zero. allocating memory with mmap for a zero length file returns a
valid pointer to the mapped region.
munmap however isn't able to remove a mapping with no
7 matches
Mail list logo
