https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #2 from Luke Kenneth Casson Leighton <lkcl at lkcl dot net> --- hi HJ, thanks for that advice - bear in mind that i am not actually directly involved in any of the projects that are experiencing these insane levels of thrashing. we (you and i) are therefore talking "to the general wider internet". so, for anyone *finding* this bugreport, HJ is recommending that, if you are a build maintainer and the linker phase is going into insane thrashing, that you try 2.30 and the option HJ recommends. now. here's the thing, HJ: distros have to "fix" the version of binutils and make it the default / standard for sometimes up to 18 months. also, there's no *guarantee* that they will ever hear about this option. can i recommend, if reports start coming in that it works, that this option be either enabled *by default*... or... that instead, there be an "auto-resident-memory detect" option similar to that used in gcc, where it detects available free resident RAM for compiling and uses that and that alone? ... and then when *that* is stable... make *that* the default. what do you think? -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
