search for: getbsssectionforglob

Hi Sanjiv, The PIC16TargetAsmInfo::getBSSSectionForGlobal apparently does magic that reinterprets the "section" field of a global in a strange way: // If GV has a sectin name or section address create that section now. if (GV->hasSection()) { std::string SectName = GV->getSection(); // If address for a variable is sp...

...----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On > Behalf Of Chris Lattner > Sent: Monday, July 20, 2009 3:21 PM > To: Sanjiv Kumar Gupta - I00171 > Cc: LLVM Developers Mailing List > Subject: [LLVMdev] PIC16TargetAsmInfo::getBSSSectionForGlobal > > > Hi Sanjiv, > > The PIC16TargetAsmInfo::getBSSSectionForGlobal apparently does magic > that reinterprets the "section" field of a global in a strange way: > > // If GV has a sectin name or section address create that section > now. > if (GV-&...

...llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev- >> bounces at cs.uiuc.edu] > On >> Behalf Of Chris Lattner >> Sent: Monday, July 20, 2009 3:21 PM >> To: Sanjiv Kumar Gupta - I00171 >> Cc: LLVM Developers Mailing List >> Subject: [LLVMdev] PIC16TargetAsmInfo::getBSSSectionForGlobal >> >> >> Hi Sanjiv, >> >> The PIC16TargetAsmInfo::getBSSSectionForGlobal apparently does magic >> that reinterprets the "section" field of a global in a strange way: >> >> // If GV has a sectin name or section address create that section...

> My short term goal is to make TargetAsmInfo not depend on libvmcore. > This means that no methods in it should take GlobalValue*'s for > example. There is a suite of GV classification methods that need to > be moved somewhere else, probably in TargetLowering or asmprinter. One > method in particular (SectionForGlobal) is virtual and only re- > implemented for