Re: rationale for bss patterns in default_section_type_flags ?

2005-06-13 Thread Brett Porter
Mike, Thanks for the feedback. We'll continue along the path we seem to agree upon... hoping we don't run into any hitches. Brett

Re: rationale for bss patterns in default_section_type_flags ?

2005-06-10 Thread Brett Porter
> > The situation is: in an embedded system, certain > > variables are placed in .persistent.bss > > Sounds like a fine name. Why not just use that name? Doing an exact match on that name in default_section_type_flags_1 is a nice solution for our needs. The reason for our query was twofold: are

Re: rationale for bss patterns in default_section_type_flags ?

2005-06-10 Thread Brett Porter
> Ultimately, people just pick names. Once picked, they form crystal > clear standards. So there is no documented standard involved. > >> No, the standard is to be prefix based, this simplifies the impact on > >> the linker scripts. > > > > Ok. So a new category of bss sections could be matche

Re: rationale for bss patterns in default_section_type_flags ?

2005-06-10 Thread Brett Porter
> > Is there a rationale for the list of bss patterns matched by > > default_section_type_flags_1 ? > > That is how bss sections are named?! Part of the question is "how bss sections are named" according to evolution, or some crystal clear standard, or what ??? > > Would matching, say, ".bss"