similar to: [LLVMdev] 2.6 release notes

On Oct 11, 2009, at 3:15 PM, John Myers wrote: > The PIC16 is an 8-bit target but under the "LLVM IR and Core > Improvements" heading it's called a 16-bit target. I think it uses 16-bit pointers though, right? I clarified in r83815. Thanks! -Chris -------------- next part -------------- An HTML attachment was scrubbed... URL:

Just a note that the 3.3 development release notes (ftp://shorewall.net/pub/shorewall/development/3.3/shorewall-3.3.0/relea senotes.txt) have a typo under the Migration Considerations. <current> /etc/shorewall/accounging. </current> <fixed> /etc/shorewall/accounting. </fixed. Regards, - Craig.

Hi, *make install* works for me on Ubuntu. Does the output of *make install* show that it was successful? Was it setup to be installed in a PATH location of Fedora? --John -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110411/8bab1522/attachment.html>

Hi, Sorry, but I cant seem to repeat the issue anymore. 'make install' works fine now. I have no idea what went wrong the first time. Thanks for the effort, and sorry to have bothered you with this. On Mon, Apr 11, 2011 at 2:25 PM, John Myers <atomicdog.jwm at gmail.com> wrote: > Hi, > > make install works for me on Ubuntu. > Does the output of make install show

John Myers <atomicdog.jwm at gmail.com> writes: > I'm looking for some pointers on how to troubleshoot this problem. I'm > trying to write a backend for the AVR. > There is an undefined reference at line 48 which is the line FrameInfo() is > on. I've tried to use the MSP430 and other targets as references so I'm not > sure > what changes I did would cause a

Hi, I'm looking for some pointers on how to troubleshoot this problem. I'm trying to write a backend for the AVR. There is an undefined reference at line 48 which is the line FrameInfo() is on. I've tried to use the MSP430 and other targets as references so I'm not sure what changes I did would cause a problem on this line? AVRTargetMachine::AVRTargetMachine(const Target &T,

On Mon, Feb 14, 2011 at 10:39 AM, Talin <viridia at gmail.com> wrote > > >> I'd like to wait until I get some feedback - I don't know yet if anyone is > having trouble building or running the thing... > Hi Talin, This is the build error I get on my ubuntu 64 bit system... john at ubuntu:~/src/build-llbrowse$ make [ 5%] Building CXX object

Hi, I just compiled llvm/clang from source on my fedora linux system as specified on the website, but running 'make' and 'make install' does not seem to result in a 'functioning' installation ? I mean, neither 'clang' or 'scan-build' seem to be found ? Are there any other actions I need to perform on my linux system in order to complete the installation

Hi, What is the Cmake equivalent to configures target option [ ./configure --target=avr-atmel-none] ? --John -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120710/5405f54b/attachment.html>

llvm no build? llvm/llvm/lib/Target/PIC16/PIC16AsmPrinter.cpp: In member function ‘bool llvm::PIC16AsmPrinter::printMachineInstruction(const llvm::MachineInstr*)’: llvm/lib/Target/PIC16/PIC16AsmPrinter.cpp:80: error: ‘CurBank’ was not declared in this scope llvm/lib/Target/PIC16/PIC16AsmPrinter.cpp: In member function ‘virtual bool llvm::PIC16AsmPrinter::runOnMachineFunction

I've been looking closely at LLVM as a means to developing a new toolchain for an MCU core of very similar architecture. To that end, the once included PIC16 backend might be a valuable reference. I found a message in April of this year that indicated it had been dropped from new releases however, and that were it to be resumed "it will be largely a rewrite". I'm wondering if

Hi XCore and PIC16 maintainers, I'd appreciate it if you guys could move your AsmPrinter implementation to be in a subdirectory like the rest of the other targets (e.g. make it live in lib/Target/PIC16/AsmPrinter). Anton is planning to move MSP430 to use the same approach. Having all the targets use the same design simplifies the build system and keeps the target architecture more

OK, so, if I understand, the tag is at 3.8.1, but there is no source drop available for download? Del From: Renato Golin [mailto:renato.golin at linaro.org] Sent: Tuesday, July 5, 2016 4:12 PM To: Del Myers <delmyers at microsoft.com> Cc: LLVM Dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] llvm 3.8.1 Release Hi Del, Yes, the tag is for the latest stable release. It's

We just wanted to check to see if they are real bugs first. We will report them if they are not already fixed. Thanks. Del From: Renato Golin [mailto:renato.golin at linaro.org] Sent: Wednesday, July 6, 2016 12:07 AM To: Del Myers <delmyers at microsoft.com> Cc: LLVM Dev <llvm-dev at lists.llvm.org> Subject: RE: [llvm-dev] llvm 3.8.1 Release Did you report the bugs? It would be a

On Sep 20, 2011, at 10:59 PM, Matthew Hilt wrote: > I've been looking closely at LLVM as a means to developing a new toolchain for an MCU core of very similar architecture. To that end, the once included PIC16 backend might be a valuable reference. I found a message in April of this year that indicated it had been dropped from new releases however, and that were it to be resumed "it

I have been analyzing the implementation for some backend (PIC16, MIPS, SPARC and MSP430) my main problem is that they are so much different, I mean obviously they are describing different architectures, but the file structure is not the same. So it is difficult to get a pattern. I have checked the available documentation files, also the video from Cardoso about how to write a backend for the

Mike Stump wrote: > llvm no build? > > llvm/llvm/lib/Target/PIC16/PIC16AsmPrinter.cpp: In member function > ‘bool llvm::PIC16AsmPrinter::printMachineInstruction(const > llvm::MachineInstr*)’: > llvm/lib/Target/PIC16/PIC16AsmPrinter.cpp:80: error: ‘CurBank’ was not > declared in this scope > llvm/lib/Target/PIC16/PIC16AsmPrinter.cpp: In member function ‘virtual >

Did you make sure localhost resolves? Also, depending on your /etc/resolv.conf, you may have to fully qualify the host's name including the DNS domain. I seem to rember having problems with this, and some combination of using localhost or hostname.domain.edu or using the actual IP address of the host cleared up the problem. Karen Wieprecht -----Original Message----- From: Noel Kelly

I have had this problem before. Never really got to the bottom of it but if you want to get on then just add '-a' to your swat command to disable authentication. -----Original Message----- From: Jim Myers [mailto:myersjj@us.ibm.com] Sent: 07 November 2002 21:08 To: SAMBA@SAMBA.ORG Subject: RE: [Samba] RE: SWAT not working, can't authenticate I had already done that, so it must be

In -help output, -help - Display available options (--help-hidden for more) Both single and double - option markers are accepted, which is good. It would probably be better to refer to options consistently using the single marker in all cases. =linearscan - linear scan register allocator =pbqp - PBQP