> From: brian@ >> > This stack exhaustion is PR36218 which was supposedly fixed on > mainline. Two problems: the fix needs to be extended to Cygwin as well > as MinGW, and you're not building mainline. > >> I wish Windows code was PIC > > zero to do with the topic of this thread.
I agree it's a tangent. It seems the PIC compilation succeeds. The whole thing where things get compiled twice, PIC and non-PIC, bugs me. It's a "great" way to slow down builds. I guess configure -only-pic might be nice. I understand the results, if only linked into an executabe, might be slower. Picking a base address that might not conflict with other code/data doesn't eliminate the problem, just reduces it, and a cost of random burning of address space. (I don't know the algorithm, "random" isn't the right word). If the code/data were really PIC, it could be tightly packed. Thanks. I'm trying it out with an 8meg stack like was applied to mingwin. I believe Solaris hosts need a fix here too. And djgpp. And perhaps others. AIX? Irix? HP-UX? *BSD? Or most systems default to 8 or 32meg? Not worth changing the gcc code to reduce or eliminate the recursion? - Jay
