Displaying 4 results from an estimated 4 matches for "sectionhint".
2010 May 04
0
[LLVMdev] MCStreamer itnerface
...the compiler would for all normal symbols,
not specify any grouping information, and allow the streamer to make
decisions about where to place data based of the content. For special
scenarios, like constructor/destructor a set of hints could be defined to
produce the expected behavior.
i.e.
struct SectionHint {};
// used by assemblers to put symbols into the
// section specified by a section directive
struct NamedSectionHint : SectionHint {
// then name of the section to put the symbol in
std::string Name;
};
struct OrderedNamedHint : NamedSection {
// the order to place the symbol into the sec...
2010 May 04
2
[LLVMdev] MCStreamer itnerface
...mlementing the
MCStreamer interface, with the caller givin the ability to give hints as to
what section to place the symbol into.
instead of SwitchSection, there would be BeginSymbol, and SymbolSymbol, it
would
be illegal to call any EmitXXX function outside of these two calls
BeginSymbol(Symbol, SectionHint)
EmitAttribute(...)
EmitAttribute(...)
...
StartFragmentEmission()
EmitFragment(...)
EmitFragment(...)
...
EndSymbol()
Object file writers would typically start recording fragments and attributes
for
a symbol on the BeginSymbol, then at EndSymbol they would evaluate what was
streamed,...
2010 May 05
3
[LLVMdev] MCStreamer interface
...he right level of semantic information. In fact, MCSection is the place that I'd start for COFF bringup.
> instead of SwitchSection, there would be BeginSymbol, and SymbolSymbol, it would
> be illegal to call any EmitXXX function outside of these two calls
>
> BeginSymbol(Symbol, SectionHint)
> EmitAttribute(...)
> EmitAttribute(...)
> ...
> StartFragmentEmission()
> EmitFragment(...)
> EmitFragment(...)
> ...
> EndSymbol()
>
> Object file writers would typically start recording fragments and attributes for
> a symbol on the BeginSymbol, th...
2010 May 05
0
[LLVMdev] MCStreamer interface
...tion between them. Should the same be true of MCSymbol, and their
data counterparts?
> > instead of SwitchSection, there would be BeginSymbol, and SymbolSymbol,
> it would
> > be illegal to call any EmitXXX function outside of these two calls
> >
> > BeginSymbol(Symbol, SectionHint)
> > EmitAttribute(...)
> > EmitAttribute(...)
> > ...
> > StartFragmentEmission()
> > EmitFragment(...)
> > EmitFragment(...)
> > ...
> > EndSymbol()
> >
> > Object file writers would typically start recording fragments and
&g...