> If you use -ffunction-sections, any function with the name> do_fork (say, a static function somewhere) will end up in> .text.do_fork function, and will be "mixed up" with> global do_fork(). For parisc it is maybe not a problem> (I am not an expert) but in other places/arches people> clearly would not want this kind of things to happen.

Erm, but we're trying to name text sections of the -ffunction-sections.We're doing this because we are trying to do a semblance of a reasonablearrangement for the relative jumps (and avoid stubs). Your patch isexplicitly breaking all of this.

> In order to handle these situations uniformly, in these patches> I decided to _never_ use .text.XXXX names for sections,> effectively leaving them "reserved for gcc's use".

We need to use the names gcc outputs, not some random name.

> Did I understand you right that in this chunk I need to> leave .text.FUNC_NAME as it was before?

Yes.

> > And thus by the same token the data transformations.> > It would be easiest for me if you will reply to the parisc patch> and indicate all parts where I should NOT do name change.