similar to: [LLVMdev] MachineBasicBlock::addLiveIn errors

Hi: After compiling rsync2.5.6 using on SVR4 on Intel HW, Please help # ./rsync --version rsync: --version: unknown option rsync error: syntax or usage error (code 1) at main.c(994) # ./rsync --help Segmentation Fault - core dumped Here is log of compilation. Script started on Sat Jun 21 05:56:15 2003 # make cc -I. -I. -g -DHAVE_CONFIG_H -I./popt -c rsync.c -o rsync.o NCR High

On Mon, Jun 11, 2012 at 1:52 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi, Again, this is more of a topic for cfe-dev (copied). LLVM itself works very well on Windows; it's Clang that has issues. > > [Synopsis: Mikael thinks Windows support is overlooked and that this is a > strategic error. You can skip to the next mail now, if you'd like :-) > Long,

Hi, [Synopsis: Mikael thinks Windows support is overlooked and that this is a strategic error. You can skip to the next mail now, if you'd like :-) Long, long, long mail follows.] Before I go on, I'd like to informally apologize for my many postings to this mailing list. I have no intentions of spamming it, but I still feel a need to grasp certain things that seem to be implied by the

On Sep 18, 2012, at 1:45 PM, Bjorn De Sutter <bjorn.desutter at elis.ugent.be> wrote: > I am working on a backend for a CGRA architecture with advanced predicate support (as on EPIC machines and as first used in the OpenIMPACT compiler). Until last month, the backend was working fine, but since the r161643 commit by stoklund, my backend doesn't work anymore. I think I noticed some

Hi, I am working on an old Unix system, UNIX SVR4 MP-RAS, running a Teradata database. Due to the age of the system (notably the C compiler, which won't handle v3 source code), I have built Samba 2.2.12 I want to use this to share Unix directories out to XP clients as network drives, for read-write access, keeping the file ownership as strict unix users. This all works fine, except for

Hi, I am working on a backend for a CGRA architecture with advanced predicate support (as on EPIC machines and as first used in the OpenIMPACT compiler). Until last month, the backend was working fine, but since the r161643 commit by stoklund, my backend doesn't work anymore. I think I noticed some related commits later on, and the assertion I get on the latest trunk (r164162) differs from

Tom, I think it might be productive to fork this thread to discuss making the requirements for upstreaming a new LLVM target more explicit and open. I'd also like to gauge interest in an idea I've discussed privately with a few community members, namely the concept of having a semi-official "incubation" system whereby proposed backends could get a trial run before becoming part

On Oct 8, 2013, at 2:06 PM, Akira Hatanaka <ahatanak at gmail.com> wrote: > What I didn't mention in r192119 is that mthi/lo clobbers the other sub-register only if the contents of hi and lo are produced by mult or other arithmetic instructions (div, madd, etc.) It doesn't have this side-effect if it is produced by another mthi/lo. So I don't think making mthi/lo clobber the