Clear the uniquing table when initializing TLOF to avoid a crash when the TLOF is reinitialized with a different MCContext.

llvm-svn: 79253

if not supported by the ELF subtarget.

llvm-svn: 79249

is why they are datarel).  This should fix PR4724, and is fallout
from r78890.

llvm-svn: 79111

them to null out the default section pointers.

llvm-svn: 79078

accidentally match unrelated things.

llvm-svn: 78966

must be emitted for PowerPC-Linux '.bss' section

llvm-svn: 78958

syntactically as a string, very similiar to what Chris did with MachO.
The parsing support and validation is not introduced yet.

llvm-svn: 78890

MCContext no longer maintains a string -> section map.

llvm-svn: 78874

them, so it doesn't have to explicitly free them.

llvm-svn: 78870

int x __attribute__((section("_foo, _bar"))) = 4;
int y __attribute__((section("_foo, _bar, 4byte_literals"))) = 1;

llvm-svn: 78867

llvm-svn: 78866

llvm-svn: 78860

llvm-svn: 78677

llvm-svn: 78576

instead of syntactically as a string.  This means that it keeps track of the 
segment, section, flags, etc directly and asmprints them in the right format.
This also includes parsing and validation support for llvm-mc and 
"attribute(section)", so we should now start getting errors about invalid 
section attributes from the compiler instead of the assembler on darwin.

Still todo: 
1) Uniquing of darwin mcsections
2) Move all the Darwin stuff out to MCSectionMachO.[cpp|h]
3) there are a few FIXMEs, for example what is the syntax to get the
   S_GB_ZEROFILL segment type?

llvm-svn: 78547

2. Move section switch printing to MCSection virtual method which takes a
   TAI.  This eliminates textual formatting stuff from TLOF.
3. Eliminate SwitchToSectionDirective, getSectionFlagsAsString, and 
   TLOFELF::AtIsCommentChar.

llvm-svn: 78510

MCSection instances.

llvm-svn: 78500

A TAI hook is appropriate in this case because this is just an
asm syntax issue, not a semantic difference. TLOF should model
the semantics of the section.

llvm-svn: 78498

give the impls an object-file-specific name.  In the future
they can take different arguments etc.

llvm-svn: 78495

now that they create *all* the sections.

llvm-svn: 78494

creation activity into the target-specific subclasses of TLOF.
Before this, globals with explicit sections could be created by
the base class.

1. make getOrCreateSection protected, add a new getExplicitSectionGlobal
   pure virtual method to assign sections to globals with a specified
   section.
2. eliminate getSpecialCasedSectionGlobals, which is now PIC specific.
3. eliminate the getKindForNamedSection virtual method, which is
   now just a static method for ELF.
4. Add implementions of getExplicitSectionGlobal for ELF/PECOFF/Darwin/PIC16.
   They are now all detangled and understandable, woo! :)

llvm-svn: 78319

getKindForGlobal.

llvm-svn: 78156

__TEXT,__ustring section on darwin.

llvm-svn: 78068

it is just being used as a prefix, so forward substitute it directly.

llvm-svn: 78067

section on ELF targets.

llvm-svn: 78066

add new concrete versions for 1/2/4-byte mergable strings.

These are not actually created yet.

llvm-svn: 78055

more step towards "semantics sections"

llvm-svn: 78002

TLOF, unifying all the dwarf targets at the same time.

llvm-svn: 77889

llvm-svn: 77888

getLSDASection() to be more specific.  This makes it pretty obvious
that the ELF LSDA section is being specified wrong in PIC mode.  We're
probably getting a lot of startup-time relocations to a readonly page,
which is expensive and bad.

Someone who cares about ELF C++ should investigate this.

llvm-svn: 77847

TAI.

llvm-svn: 77842

llvm-svn: 77834

compute it based on what it knows.  As part of this, rename getSectionForMergeableConstant
to getSectionForConstant because it works for non-mergable constants also.

The only functionality change from this is that Xcore will start dropping
its jump tables into readonly section instead of data section in -static mode.
This should be fine as the linker resolves the relocations.  If this is a
problem, let me know and we'll come up with another solution.

llvm-svn: 77833

the appropriate subclasses.

llvm-svn: 77815

llvm-svn: 77814

llvm-svn: 77813

llvm-svn: 77812

llvm-svn: 77810

should have no state that is specific to particular globals in the
section.  In this case, it means the removal of the "isWeak" and
"ExplicitSection" bits.  MCSection uses the new form of SectionKind.

To handle isWeak, I introduced a new SectionInfo class, which is
SectionKind + isWeak, and it is used by the part of the code generator
that does classification of a specific global.

The ExplicitSection disappears.  It is moved onto MCSection as a new
"IsDirective" bit.  Since the Name of a section is either a section
or directive, it makes sense to keep this bit in MCSection.  Ultimately
the creator of MCSection should canonicalize (e.g.) .text to whatever
the actual section is.

llvm-svn: 77803

llvm-svn: 77787