search for: div8

We have two subnets with two samba servers (div0 - 150.10.10.1 and div8 - 150.18.18.1 ). If I break the connection between subnets, clients belong to div8 cannot connect locally. All clients have set up wins server to 150.10.10.1 ( div0 ) . If subnets are connect, all is ok ( connecting, browsing). We are using samba 1.9.18p7. smb.conf in div0 is [global] workgroup...

...etect when a real 32-bit divide is happening. There is no way to write an 8-bit divide in C; it's a 32-bit divide where each operand happens to be a sign extension from an 8-bit type. > If someone knows where the 8-bit DIV is being handled in the IR I could look into this change? For your div8 testcase, instcombine transforms from a "udiv i32" to a "udiv i8". instcombine isn't allowed to do that for "sdiv i32" because it potentially introduces undefined behavior. -Eli

Hi, I noticed that when dividing with signed 8-bit values the IR uses a 32-bit signed divide, however, when unsigned 8-bit values are used the IR uses an 8-bit unsigned divide. Why not use a 8-bit signed divide when using 8-bit signed values? Here is the C code and IR: char idiv8(char a, char b) { char c = a / b; return c; } define signext i8 @idiv8(i8 signext %a, i8 signext %b) nounwind readnone { entry: %conv = sext i8 %a to i32 %conv1 = sext i8 %b to i32 %div = sdiv i32 %conv, %conv1 %conv2 = trunc i32 %div to i8 ret i8 %conv2 } unsigned char div8(unsigne...

I understand, but this sounds like legalization. Does every architecture trigger an overflow exception, as opposed to setting a bit? Perhaps it makes more sense to do this in the backends that trigger an overflow exception? I'm working on a modification for DIV right now in the x86 backend for Intel Atom that will improve performance, however because the *actual* operation has been replaced