search for: _pic

Hi Folks - I''m pretty new to ACPI (don''t know my ASL from a hole in the ground :-), but I think the _PRT method has the PIC/APIC cases reversed. I''m looking at tools/firmware/acpi/acpi_dsdt.asl. The ACPI spec says a _PIC method (if defined) will be called with an argument of 1 if the host is using APIC interrupts. If the host is using PIC interrupts instead, it will either not call the _PIC method, or will call it with an argument of 0. The current _PIC method simply stores its argument into the PICD variable:...

OCaml has a small runtime which is statically linked into the virt tools (providing things like GC and primitives). Since OCaml 4.03 it has been possible to select variants of this runtime, one of which is compiled with -fPIC, using ‘ocamlopt -runtime-variant _pic’. This has performance implications on i686, but is relatively free on other architectures. Since it (in theory) adds to the security of the final binary this commit enables it whenever it is available. --- .gitignore | 1 + configure.ac | 2 ++ m4/g...

We also use -runtime-variant _pic which selects the OCaml runtime linked with -fPIC. This will cause a performance regression on i686 although that probably doesn't matter now. A bigger issue is that it will stop supermin from building with older versions of OCaml (<= 4.02.2). We might instead try detecting if it's th...

...l_plugin.ml + $(OCAMLOPT) $(OCAMLOPTFLAGS) -I ../plugins/ocaml -c $< -o $@ +test-ocaml-plugin.so: test_ocaml_plugin.cmx ../plugins/ocaml/libnbdkitocaml.la ../plugins/ocaml/NBDKit.cmi ../plugins/ocaml/NBDKit.cmx $(OCAMLOPT) $(OCAMLOPTFLAGS) -I ../plugins/ocaml \ -output-obj -runtime-variant _pic -o $@ \ NBDKit.cmx $< \ -- 2.17.2

On Friday, 31 August 2018 10:03:31 CEST Richard W.M. Jones wrote: > We also use -runtime-variant _pic which selects the OCaml runtime > linked with -fPIC. This will cause a performance regression on i686 > although that probably doesn't matter now. This is for supermin, right? > A bigger issue is that it will stop supermin from building with older > versions of OCaml (<= 4.02....

...hat's perhaps theoretical, as I don't think anyone is really compiling them with such an old compiler). This causes a bunch of trouble. To my mind the major things are: - Having to have the "Bytes" compatibility module (added in OCaml 4.02). - Conditional on -runtime-variant _pic (added in OCaml 4.03). - Not being able to use ppx extension points, which means we have lots of repetitive string_of_* functions that could be mostly eliminated (needs OCaml >= 4.02). - Match + catch (needs OCaml >= 4.02) https://blog.janestreet.com/pattern-matching-and-exceptio...

...it2 split3 -MAINTAINERCLEANFILES += split1 split2 split3 +CLEANFILES += split1 split2 split3 split1: file-data rm -f $@ $@-t dd if=$< of=$@-t bs=1 count=100 @@ -528,6 +530,10 @@ test-ocaml-plugin.so: test_ocaml_plugin.cmx ../plugins/ocaml/libnbdkitocaml.la . -output-obj -runtime-variant _pic -o $@ \ NBDKit.cmx $< \ -cclib -L../plugins/ocaml/.libs -cclib -lnbdkitocaml +CLEANFILES += \ + test_ocaml_plugin.cmx \ + test_ocaml_plugin.cmi \ + test-ocaml-plugin.so endif HAVE_OCAML @@ -585,7 +591,7 @@ endif HAVE_RUBY # Shell (sh) plugin test. LIBGUESTFS_TESTS += test-shell che...

...P80D...h..p}{P80 3230: 44 0c ff ff ff 00 00 79 69 0a 18 00 00 50 38 30 D......yi....P80 3240: 44 70 50 38 30 44 50 38 30 48 5b 80 53 50 52 54 DpP80DP80H[.SPRT 3250: 01 0a b2 0a 02 5b 81 0b 53 50 52 54 11 53 53 4d .....[..SPRT.SSM 3260: 50 08 14 12 5f 50 49 43 01 70 68 47 50 49 43 70 P..._PIC.phGPICp 3270: 68 50 49 43 4d 14 47 0c 5f 50 54 53 01 70 00 50 hPICM.G._PTS.p.P 3280: 38 30 44 50 38 58 48 00 68 70 5c 2f 05 5f 53 42 80DP8XH.hp\/._SB 3290: 5f 50 43 49 30 4c 50 43 42 48 5f 45 43 42 31 44 _PCI0LPCBH_ECB1D 32a0: 46 5c 2e 5f 53 42 5f 42 46 43 43 a0 43 06 93 68 F\._SB_BFCC....