My gcc-3.x cross-compiler does not produce that same bad code.
(My gcc build is from cvs as of March 15.)
Even if there is something wrong with the code, gcc is definitely behaving
badly. Here is the code from your hurdselect.s that should correspond to
the initialization of INTTYPE.
.LM240:
On Sun, Mar 31, 2002 at 09:45:07PM +0200, Niels Möller wrote:
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
>
> What's the definition of mach_msg_type_t? I have the Hurd sources, but
> not Mach sources, around.
typedef struct {
unsigned intmsgt_name : 8,
msg
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
What's the definition of mach_msg_type_t? I have the Hurd sources, but
not Mach sources, around.
> On Sun, Mar 31, 2002 at 01:59:56AM +0100, Marcus Brinkmann wrote:
> > ok, here is some hard data. It turns out that the comparison:
> >*(int *) &ms
On Sun, Mar 31, 2002 at 01:59:56AM +0100, Marcus Brinkmann wrote:
> ok, here is some hard data. It turns out that the comparison:
>*(int *) &msg.error.err_type == *(int *) &inttype
>
> is failing, with the correct number 268509186 on the left hand and a bogus
> number 65536 on the right hand
