search for: karahalios

...ck-end for a fictitious target machine - something similar to "Porting GCC for Dunces" (http://ftp.axis.se/pub/users/hp/pgccfd/pgccfd.pdf ). Also a pre-made "Dummy" back-end that had some basic instructions would also go a long way in helping someone write a back-end. Alex Karahalios On Apr 11, 2009, at 5:03 PM, Greg McGary wrote: > As we've already seen, David Chisnall prefers hacking LLVM over GCC > (see http://www.informit.com/articles/article.aspx?p=1215438): "In > contrast, every time I look at the GCC code, it takes two people to > prevent me fr...

As we've already seen, David Chisnall prefers hacking LLVM over GCC (see http://www.informit.com/articles/article.aspx?p=1215438): "In contrast, every time I look at the GCC code, it takes two people to prevent me from clawing my eyeballs out." I'm sorry to report that so-far I have had the opposite experience. Some years ago, I ported binutils (via CGEN) and GCC to an

Hello, Alex > for generating C++ records. I was hoping for something that would allow me > to specify my target machine (more inline with what GCC does) and then just > stand back and watch the target code be generated. I guess a deeper > understanding of Target classes is mandatory before proceeding to use > TableGen. That's true. TableGen can automate many important cases,

Hi Sanjiv, Assuming that that support for Ada in LLVM is complete, I would look to see if there is something that is done there. Ada provides two pragmas (Interrupt_Handler & Attach_Handler) which allow you to both statically and dynamically attach interrupts to procedures. Alex Karahalios On Jul 21, 2009, at 8:07 AM, <Sanjiv.Gupta at microchip.com> <Sanjiv.Gupta at microchip.com > wrote: > Apparently, there is no explicit support for ISRs in the llvm > framework. I could not find a matching attribute that can be used > to mark a function as an ISR, whic...

Hi, Apparently, there is no explicit support for ISRs in the llvm framework. I could not find a matching attribute that can be used to mark a function as an ISR, which codegen and optimizer can use accordingly. ISRs aren't called explicity from any function, so currently the optimizer deletes them. We are planning to introduce a new "interrupt" attribute (to be modeled similiar to