search for: cgo

FYI, The LLVM Performance Workshop will be held at CGO 2017. The workshop is co-located with CC, HPCA, and PPoPP. If you are interested in attending the workshop, please register at the CGO website: http://cgo.org/cgo2017/workshops.html When: Saturday February 4th, 2017 Where: Austin, Texas, USA ---- Hi, CGO workshop and tutorial organizers, This i...

An LLVM Performance Workshop will be held at CGO 2017. The workshop is co-located with CC, HPCA, and PPoPP. If you are interested in attending the workshop, please register at the CGO website: http://cgo.org/cgo2017/workshops.html Call for Speakers We invite speakers from academia and industry to present their work on the following list of top...

Hi all, The slides we used on "CGO MCLinker and LLVM Tutorial" are now available on the MCLinker website: http://code.google.com/p/mclinker/wiki/2013CGOTutorial Enjoy! - The CGO Tutorial on MCLinker and LLVM 2013 committee

(Apologies if you receive multiple copies of this announcement) CGO 2011 - CALL FOR PAPERS Ninth Annual IEEE/ACM International Symposium on Code Generation and Optimization (CGO 2011) April 2-6, 2011, Chamonix, France http://www.cgo.org The International Symposium on Code Generation and Optimization (CGO) brings together researchers and practitioners working o...

Dear LLVM user and developer, We get a chance to give a tutorial on LLVM and MCLinker. The tutorial will be co-located with CGO 2013 on Feb. 24 (Sunday morning) in Shenzhen, China. If you are also interesting in these topics, welcome to join the tutorial! Here is a website of the tutorial: http://code.google.com/p/mclinker/ We're also looking for additional presenters to share a section about LLVM target backend o...

In the past, I've just referenced Chris's CGO 2004 paper when referring to LLVM: C. Lattner and V. Adve. LLVM: A compilation framework for lifelong program analysis & transformation. For sub-projects like Clang and DragonEgg, I just cite the URLs: [4] Clang. clang.llvm.org. [5] DragonEgg. dragonegg.llvm.org. I don't know of any can...

On 4/14/13 3:35 PM, Justin Holewinski wrote: > In the past, I've just referenced Chris's CGO 2004 paper when > referring to LLVM: I second that. We at Illinois typically cite Chris's CGO paper. The bibtex is: @InProceedings{LLVM:CGO04, Author = {Chris Lattner and Vikram Adve}, Title = {{LLVM}: A Compilation Framework for Lifelong Program Analysis and Transformation}...

Hi everyone, I would like to share a paper my co-authors and I published at CGO 2013, where we used profiling support in LLVM for efficient code layout randomization: Andrei Homescu, Steven Neisius, Per Larsen, Stefan Brunthaler, Michael Franz. Profile-guided Automated Software Diversity. In Proceedings of the 2013 International Symposium on Code Generation and Optimization, C...

...e's the general boilerplate that will be approx the same for all plugins with cut+paste tedium across projects, and then there's the "interesting" code in test.go The methods in test.go though look quite unappealing from a Go programmer's POV, as the API contracts are full of CGo types and unsafe pointers. To make something that is attractive for Go programmers, I think it needs to hide all the low level CGo stuff entirely. Implementing a nbdkit plugin should require nothing more that providing pure Go code that satisfies a well defined Go "interface" type defi...

Hello, when i use libguestfs to ceph rbd by golang, but there has panic: panic: runtime error: cgo argument has Go pointer to Go pointer goroutine 1 [running]: guestfs.(*Guestfs).Add_drive.func11(0xc000010028, 0xcda6a0, 0xc0000d6000, 0xc000090280) /opt/gopath/src/guestfs/guestfs.go:1440 +0xc2 guestfs.(*Guestfs).Add_drive(0xc000010028, 0x7ffd4b5d67ff, 0xd, 0xc00008d9d8, 0x0) /opt/gopath/src/gue...

...Instead we can set PKG_CONFIG to point to > > a fake pkg-config binary which will return the correct CFLAGS. > > > > Fixes: commit 1ff44288ae1cf95428283e252edd9474c3fe3b55 > > Thanks: Dan Berrangé, Eric Blake > > > +# This fake pkg-config program is used to trick cgo so that > > +# "#cgo pkg-config nbdkit" lines are processed relative to the local > > +# directory and not the installed nbdkit. > > + > > +case "$1" in > > + --cflags*) echo "-I@abs_top_builddir@/include" ;; > > + *) ;; > &...

...ON) HOWEVER CAUSED AND +# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT +# OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. + +# This fake pkg-config program is used to trick cgo so that +# "#cgo pkg-config nbdkit" lines are processed relative to the local +# directory and not the installed nbdkit. + +case "$1" in + --cflags*) echo "-I@abs_top_builddir@/include" ;; + *) ;; +esac -- 2.18.2

...gt; On Oct 28, 2008, at 10:10 AM, 谭明星 wrote: >> >> PS: The following are links about this paper: >> http://portal.acm.org/citation.cfm?id=1356064 >> http://www.if.insa-lyon.fr/chercheurs/jpbabau/emsoc/presentations/EmSoC07_Boissinot.pdf >> I've put the slides from CGO online: http://perso.ens-lyon.fr/benoit.boissinot/upload/bboissin-liveness-cgo-slides.pdf They should be much better than the one from my presentation at EmSoC. regards, Benoit

Could you please convert the PowerPoint slides to PDF and have them there as an alternative? -- Sean Silva

Hey, I noticed this talk from the EuroLLVM 2015 (https://llvm.org/devmtg/2015-04/slides/pslp_slides_EUROLLVM2015.pdf) on the PSLP vectorization algorithm (CGO 2015 paper: http://vporpo.me/papers/pslp_cgo2015.pdf). Is anyone working on implementing it? If so, are there Phab reviews I can subscribe to? Best, Matt

...hine learning approaches to ARchitecture and compilaTion (SMART 2011) http://cTuning.org/workshop-smart2011 April 2nd or 3rd, 2011, Chamonix, France (co-located with CGO 2011 Conference) ******************************************************************************** The rapid rate of architectural change and the large diversity of architecture features has made it increasingly difficult for compiler writers to keep pace with microprocessor evolution. This problem...

....org/docs, some papers > on http://www.llvm.org/pubs/ and some source code in LLVM2.3. The > live variables analysis in LLVM seems not very efficient, and the > algorithm presented in Benoit Boissinot, Fast liveness checking for > ssa-form programs (the best paper of ACM SIGPLAN CGO’08) is much > better, especially for JIT compilation. So, I want to implement > this algorithm in LLVM, which is also planed to be my final project > in “Advance Compiler Techniques” class. > To my knowledge, there has been complete dominator tree > implementation in LLVM2.3...

...e some kind of module loading instead? No, I was mostly meaning the "copylib" approach to plugins, where the plugin author owns the whole stack. I was just thinking of what the "ideal" would be from a Go programmers POV, and that I think involves the least possible exposure to CGo and the native nbdkit APIs. > > Looking at the code below there's the general boilerplate that > > will be approx the same for all plugins with cut+paste tedium > > across projects, and then there's the "interesting" code in > > test.go > > > &gt...

...GoLang.ml b/generator/GoLang.ml index 73df5254..55ff1b8a 100644 --- a/generator/GoLang.ml +++ b/generator/GoLang.ml @@ -517,10 +517,10 @@ let func copy_uint32_array(entries *C.uint32_t, count C.size_t) []uint32 { ret := make([]uint32, int(count)) - // See https://github.com/golang/go/wiki/cgo#turning-c-arrays-into-go-slices - // TODO: Use unsafe.Slice() when we require Go 1.17. - s := (*[1 << 30]uint32)(unsafe.Pointer(entries))[:count:count] - copy(ret, s) + s := unsafe.Slice(entries, count) + for i, item := range s { + ret[i] = uint32(item) + } retur...

...ile system. >> I think that golang bindings need separate repo, may be autogenerate >> bindings and push resulted files to separate github repo.... In this >> case peaples can do go get github.com/libguestfs/go-libguestfs and >> have a package. And build it with or without CGO_ENABLED (static or >> dynamic). But in case of autogenerated binding i don't know how to >> write docs and keep it sync with code... > > The trouble with a separate repository is that it would quickly go out > of date compared to the current API. That's why we strongly...