Article View: gnu.gcc.help
Article #41788libg++ fails tBitSet on DEC ALPHA OSF/1 3.2B
From: smcdowall
Date: Mon, 19 Feb 1996 00:00
Date: Mon, 19 Feb 1996 00:00
42 lines
1756 bytes
1756 bytes
Hmm..Where do I post libg++ errors?? 1) The "tBitSet" test case fails on my DEC Alpha 32.B w/ G++ 2.7.2 with this error: tBitSet.cc:101: failed assertion `c[i+1] == 0' BitSet tests: a = 0* b = 000000000010* c = 1010101010101010101010101010101010101010* BITSETBITS = 64 c[i + 1] != 0 @ i+1 = 31 c[i+1] = 1 Now, my guess is the following... DEC ALPHA is a Big Endian type arch. (well, not the "normal" one anyway).. so I think it has something to do w/ that.. It may also have to do w/ ULONGS = 64 bits (was 32 only supported?) If this helps, I wrote a little program to store 0x123456789ABCDEFF and then print it out using char *'s (ie: in byte order..) here is the result ULONG 0x123456789ABCDEFF = ff de bc 9a 78 56 34 12 So this may be a hint of the problem too.. 2) Also, I noticed some compile errors in the librx stuff (well, warnings anyway) about pointers being cast to ints, etc. On an ALPHA, a pointer is 64 bits and ints are 32 .... Does libg++ really (and it appears it does) assume sizeof(ints) == sizeof(char *) ?? Is anyone fixing this assumption?? Thanks for any info / help... -Steve --- Steven J. McDowall | email: smcdowall@globalMT.com global MAINTECH, inc. | voice: 612.944-0400 6468 City W. Pkwy | fax: 612.944-3311 Eden Praire MN 55344 |
Technical Details
Message-ID:
<4ga9ca$1s2@wavefront.wavefront.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,24e09d94313b5ee2,start X-Google-Attributes: gid11318c,public From: smcdowall@globalmt.com Subject: libg++ fails tBitSet on DEC ALPHA OSF/1 3.2B Date: 1996/02/19 Message-ID: <4ga9ca$1s2@wavefront.wavefront.com> X-Deja-AN: 140117780 organization: WaveFront Communications, Inc. newsgroups: gnu.gcc.help