search for: integer32

Hi, I'm lowering some of the logical operators (by example the | operator) on integer32. Sadly my target only provide native instruction on high and low parts of 32 bits registers. So, I have to generate a sequence of two native instructions (LOR followed by HOR). I've introduced an Pseudo instruction with a custom inserter. def OR_A_oo : CLPPseudoInst<(ins FPUaOff...

...recompiled, and could keep on working as already do. So we would not introduce backward incompatible change. *** FINAL KEY IDEA *** Take already developed "bit64" Package (https://github.com/cran/bit64) as base for building a new Integer64 Type System which co-exists natively in R with Integer32 (Just as "parallel" package was included in the past into base R for example), and build on top of it improvements.

...applies to extending existing ones. Sometimes it helps to generate a new one for a currently-partially-supported device, and then compare with existing subdriver (using meld or similar GUI helps a lot) to port the missing lines into it. In computers all numbers are binary :) In SNMP they should be Integer32 or Integer64 type, I think. Do you know which APC MIB version that NMC supports, and if that MIB's text contradicts the reality (an APC bug to report to them, I guess). In the nut2mib structures you can specify several sources for the same reading name, which allows the same subdriver to &quot...

...sting ones. Sometimes it helps to generate > a new one for a currently-partially-supported device, and then compare with > existing subdriver (using meld or similar GUI helps a lot) to port the > missing lines into it. > > In computers all numbers are binary :) In SNMP they should be Integer32 or > Integer64 type, I think. Do you know which APC MIB version that NMC > supports, and if that MIB's text contradicts the reality (an APC bug to > report to them, I guess). > > In the nut2mib structures you can specify several sources for the same > reading name, which allow...

So what would it take me to edit NUT's code for my case to work? My Network Management Card sends its output state using unfortunately only (I guess so) this OID: 1.3.6.1.4.1.318.1.1.1.11.1.1.0 Weirdly the standard way of obtaining Battery Status (drivers/apc-mib.c) 1.3.6.1.4.1.318.1.1.1.2.1.1.0 gives me good results. Unfortunately power status OID's value type differs (my: 64 digits