similar to: [LLVMdev] pkg-config

Here's some instructions for installing hogg on a current Ubuntu 8.10 (or Debian unstable? testing?) system, ie. if you don't already have haskell's cabal system installed: $ sudo apt-get install ghc6 $ wget http://hackage.haskell.org/packages/archive/cabal-install/0.6.0/cabal-install-0.6.0.tar.gz $ tar zxf cabal-install-0.6.0.tar.gz $ cd cabal-install-0.6.0 $ ./bootstrap.sh $ cabal

HOgg 0.4.1 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the fourth public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on

Conrad Parker wrote: > Here's some instructions for installing hogg on a current Ubuntu 8.10 > (or Debian unstable? testing?) system, ie. if you don't already have > haskell's cabal system installed: > > $ sudo apt-get install ghc6 > $ wget http://hackage.haskell.org/packages/archive/cabal-install/0.6.0/cabal-install-0.6.0.tar.gz > $ tar zxf

HOgg 0.4.1.1 Released --------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the fifth public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly

HOgg 0.2.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. http://snapper.kfish.org/~conrad/software/hogg/ This is the initial public release. The focus is on correctness of Ogg parsing and production. The capabilities of the hogg commandline tool are roughly on par with those of the oggz* tools[0],

HOgg 0.3.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the second public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on

HOgg 0.3.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the second public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on

HOgg 0.4.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the third public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on

I want to generate Haskell bindings to LLVM intrinsics. In a first attempt I wrote a little parser that reads IntrinsicsX86.td and outputs a Haskell module. E.g. the definition def int_x86_avx_max_ps_256 : GCCBuiltin<"__builtin_ia32_maxps256">, Intrinsic<[llvm_v8f32_ty], [llvm_v8f32_ty, llvm_v8f32_ty], [IntrNoMem]>; is turned into

It has been a while since I've announced a pandoc release on this list, so here's an update. The latest version of pandoc supports conversion of markdown to a host of other formats, including * HTML formats: XHTML, HTML5, and HTML slide shows using Slidy, S5, or DZSlides * Word processor formats: Microsoft Word docx, OpenOffice odt * Ebooks: EPUB * Documentation formats: DocBook, GNU

Henning, I believe the code that is supposed to do this is in: lib/Target/X86/X86Subtarget.cpp in X86Subtarget::AutoDetectSubtargetFeatures() Is there a bug in that function? -Hal On Thu, 24 May 2012 23:56:48 +0200 (CEST) Henning Thielemann <llvm at henning-thielemann.de> wrote: > > On Thu, 24 May 2012, Pan, Wei wrote: > > > Very likely AVX is not enabled in your llc.

Henning, Are you looking at trunk? I believe that in trunk this has been uncommented. -Hal On Fri, 25 May 2012 00:47:42 +0200 (CEST) Henning Thielemann <llvm at henning-thielemann.de> wrote: > > On Thu, 24 May 2012, Hal Finkel wrote: > > > Henning, > > > > I believe the code that is supposed to do this is in: > > lib/Target/X86/X86Subtarget.cpp in >

On Thu, 24 May 2012, Pan, Wei wrote: > Very likely AVX is not enabled in your llc. This feature was enabled > just recently (late of April). I forgot to mention that I am using recent LLVM-3.1 and in principle my llc knows about avx as I have shown in the second example. But avx does not seem to be used by default. On Thu, 24 May 2012, Henning Thielemann wrote: > $ llc -o - -mattr

On Thu, 24 May 2012, Hal Finkel wrote: > Henning, > > I believe the code that is supposed to do this is in: > lib/Target/X86/X86Subtarget.cpp in > X86Subtarget::AutoDetectSubtargetFeatures() > Is there a bug in that function? I read there: // FIXME: AVX codegen support is not ready. //if ((ECX >> 28) & 1) { X86SSELevel = AVX; ToggleFeature(X86::FeatureAVX); }

=== not on the list, please cc === Greetings. I've STFW, and I've realy not seen any reference to this. Recently I changed from loglevel info to loglevel debug. After I did that, I started getting a PLETHERA of odd logs. I changed back to LogLevel INFO, but I do stil get these messages, which kinda worry me: Jul 11 10:10:13 cabal sshd[26003]: debug: tvp!=NULL kid 0 mili 10 Jul 11

Hi all, Here is a patch to user pkg-config (if available) to detect libogg and fall back to old method if pkg-config fails. Pkg-config has the advantage that it can do configured to do the right thing when cross-compiling. Erik --- m4/Makefile.am | 4 ++ m4/extra_pkg.m4 | 85 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 89 insertions(+), 0 deletions(-)

Hi all, Here is a patch to user pkg-config (if available) to detect libogg and fall back to old method if pkg-config fails. Pkg-config has the advantage that it can do configured to do the right thing when cross-compiling. Erik --- Makefile.am | 4 +- autogen.sh | 15 ++++++++++ configure.ac | 14 ++++++++- m4/Makefile.am | 4 ++ m4/extra_pkg.m4 | 85

Hi all, I have some old code using the JIT via the LLVM-3.0-C API. I want to upgrade to newer versions of LLVM. As a simple example I wrote a C program that creates the following function and calls it: ; ModuleID = 'round-avx.bc' target triple = "x86_64-pc-linux-gnu" define void @round(<8 x float>*) { _L1: %1 = load <8 x float>* %0 %2 = call <8 x

Hi all, it's Advent time and I took the opportunity to program a song for you. The sound, i.e. speech synthesis and reverb, is rendered by the LLVM-JIT and the synthesizer is controlled via ALSA-MIDI by the Haskell live sequencer. http://www.youtube.com/watch?v=0EQCgi5qa3E "Alta trinita beata" You find additional information in the video description. Best, Henning

https://bugzilla.mindrot.org/show_bug.cgi?id=1996 Bug #: 1996 Summary: pkg-config tweaks for cross-compiling Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Build system