similar to: [LLVMdev] debian

On Sat, May 14, 2005 at 02:18:26AM +0200, Stefan Strasser wrote: > in case you're interested in having llvm in debian sarge: it was > removed today. I don't know why, but you might want to find out > because sarge is in freeze phase for release next month. Possibly because of these: http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=llvm I addressed the first one and fixed it in

Hi! On 2020-06-16 12:37 -0000, Stuart Henderson wrote: > On 2020-06-15, Alexander Strasser <eclipse7 at gmx.net> wrote: > > I had some imap crashes (sig11) starting at the end of 2019 after > > an upgrade of dovecot. > > > > I found out, that I didn't have any problems using version v2.3.8, > > but any version v2.3.9 and higher would trigger the crashes.

I've encountered a few bugs including ICE and reject-valid when compiling a program with llvmg++ which compiles fine with standalone g++. Should I report those to your bugzilla or is it likely that these bugs are gcc bugs in the version of gcc you're using? if so, are there any plans to port the frontend to a newer gcc? (gcc 4.0 will be out in a few weeks) the versions: llvm 1.4 from

Hi! What's the plan for support on Linux 64-bit machines? Is that actively being worked on right now or is there a roadmap for doing this? Thanks! -bw

Markus F.X.J. Oberhumer schrieb: > The reason behind this is that llvm-gcc is based on a pre-3.4 snapshot > ("3.4-llvm 20030924") then it's not unlikely that these are llvm bugs since my code also compiles with gcc 3.3 filed PR 551 and 552 -- Stefan Strasser

Markus F.X.J. Oberhumer schrieb: > Stefan Strasser wrote: > >> I've encountered a few bugs including ICE and reject-valid when >> compiling a program with llvmg++ which compiles fine with standalone g++. >> >> Should I report those to your bugzilla or is it likely that these bugs >> are gcc bugs in the version of gcc you're using? >> if so, are

Dear All, Here's a question Vikram and I received. Is the LLVM JIT thread safe? -- John T. -------------- next part -------------- An embedded message was scrubbed... From: "Adve, Vikram Sadanand" <vadve at uiuc.edu> Subject: Fwd: LLVM and threading Date: Thu, 1 Nov 2007 09:48:59 -0500 Size: 3037 URL:

Looking through http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xen I think it would be useful to add some usertags, in particular to easily filter for toolstack specific (i.e xend) bugs. I think we can use the pkg-xen-devel at lists.alioth.debian.org namespace for this -- what do you think? Ian.

Hi List, I am in the preliminary stages of adding a JIT compiler to a sizable Scheme system (PLT Scheme). The original plan was to use GNU Lightning, but 1) it seems to be dead, and 2) LLVM has already done a huge amount of stuff that I would have had to write (poorly) from scratch. At the moment, LLVM seems to be the ideal choice for implementing the Scheme JIT, but there are problems that need

user pkg-xen-devel@lists.alioth.debian.org usertag 271051 + close-after-first-upload usertag 326817 + probably-unreproducible usertag 331297 + probably-fixed usertag 321154 + probably-fixed usertag 327493 + pending-in-svn usertag 342249 + pending-in-svn usertag 321157 + pending-in-svn usertag 323698 + pending-in-svn thanks Hi! I'm user-tagging some of the bugs in the bts so we can keep a

One other note I forgot... sig_sysreturn (arch/x86/kernel/signal_32.c) has a magic fudge factor to fix up stack layout differences between llvm and gcc. If when you hit userspace you get signal handling errors, look at the frame addresses printed out and adjust the fudge factor to make the frame addresses match. (the code automatically enables the debug output after the first signal frame

Hi all! This is my first post on this list. Please pardon me if I overlooked or misunderstood some things. I had some imap crashes (sig11) starting at the end of 2019 after an upgrade of dovecot. I found out, that I didn't have any problems using version v2.3.8, but any version v2.3.9 and higher would trigger the crashes. After investigating more deeply and creating a core dump, I saw that

On 2020-06-16 20:32 +0200, Alexander Strasser wrote: > On 2020-06-16 12:37 -0000, Stuart Henderson wrote: > > On 2020-06-15, Alexander Strasser <eclipse7 at gmx.net> wrote: > > > I had some imap crashes (sig11) starting at the end of 2019 after > > > an upgrade of dovecot. > > > > > > I found out, that I didn't have any problems using version

Conditional Inference Procedures in a Permutation Test Framework The `coin' package implements a general framework for conditional inference procedures, commonly known as permutation tests, theoretically derived by Strasser & Weber (1999). The conditional expectation and covariance for a broad class of multivariate linear statistics as well as the corresponding multivariate limiting

Conditional Inference Procedures in a Permutation Test Framework The `coin' package implements a general framework for conditional inference procedures, commonly known as permutation tests, theoretically derived by Strasser & Weber (1999). The conditional expectation and covariance for a broad class of multivariate linear statistics as well as the corresponding multivariate limiting

On Sat, 2005-02-26 at 22:34 -0600, Chris Lattner wrote: > On Sat, 26 Feb 2005, Tanu Sharma wrote: > > > Thanks for the reply :-) > > I am actually looking for ways to determine "size" of code segment when the program is in native code. > > Any suggestions to do that ? > > Compile it with llvm to a native .o or .exe file, then run 'size' on it? >

For people who want to try hacking on the linux kernel with llvm, here is a head start: http://llvm.org/~alenhar2/k.tbz This is a 2.6.27.5 kernel with a .config file for qemu/kvm with virtio devices (I also think it will work with the default devices). The build process uses llvm-gcc -> opt -> llc so you can add your own (per-file) passes to the build process or debug specific passes.

Hello, Years ago, I used Monit to monitor Asterisk and restart it whenever it failed. Now, I wonder which tool I should pick for an Debian 8 (current) or CentOS 7 (future) environment. The main reason I'm looking for this tool is to avoid as much as possible, current 5 minutes delay between Asterisk's stop and first cutomers complains. 1. I always install Asterisk from source but

On Fri, Aug 16, 2013 at 03:16:49PM +0100, Ian Campbell wrote: > Looking through http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xen I > think it would be useful to add some usertags, in particular to easily > filter for toolstack specific (i.e xend) bugs. I've never seen the use for this. The kernel team tried and it did not work well. The release team however uses them and like it.

Hi, there are quite some ancient xen bug reports filed against packages that the BTS does not know (any longer) since they have been removed. I would appreciate it if you could take a look at the xen bugs (mostly xen 3.x stuff that was neither reassigned to xen 4 nor closed at the time xen3 was removed) and either reassign them to existing (source) packages or close them. The complete list of