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
Chris Lattner wrote:> > 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 >Sure. I'll take care of that once I get my hands off a few other things that we want to finish. As you have already guessed correctly, that isn't likely to be soon. - Sanjiv
On Aug 13, 2009, at 11:34 AM, Sanjiv Gupta wrote:>> >> 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 once I get my hands off a few other > things that we want to finish. As you have already guessed > correctly, that isn't likely to be soon.Great thanks! Again, no hurry. I appreciate it, -Chris