search for: mcsectionpic16

On Aug 12, 2009, at 9:48 PM, Sanjiv.Gupta at microchip.com wrote: > Chris, > I will try to get it done before 2.6. (8/21). > Thanks Sanjiv! One other nice cleanup (but which is not time critical at all) would be to merge the contents of "PIC16Section" into the new "MCSectionPIC16" class. Unlike the previous design, you're now allowed to store arbitrary data in your target-specific section class, which should simplify a lot of awkward code that PIC16 had to have to work around the old design. -Chris

...Sanjiv.Gupta at microchip.com wrote: > >> Chris, >> I will try to get it done before 2.6. (8/21). >> > > Thanks Sanjiv! One other nice cleanup (but which is not time critical > at all) would be to merge the contents of "PIC16Section" into the new > "MCSectionPIC16" class. Unlike the previous design, you're now allowed > to store arbitrary data in your target-specific section class, which > should simplify a lot of awkward code that PIC16 had to have to work > around the old design. > > -Chris > Sure. I'll take care of that o...

Chris, I will try to get it done before 2.6. (8/21). - Sanjiv -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu on behalf of Chris Lattner Sent: Wed 8/12/2009 10:08 PM To: LLVM Developers Mailing List Subject: [LLVMdev] XCore & PIC16 AsmPrinters Hi XCore and PIC16 maintainers, I'd appreciate it if you guys could move your AsmPrinter implementation to be in a

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