On Tue, Feb 23, 2021 at 2:17 AM Alexandre Oliva <ol...@adacore.com> wrote:
> I take your response as confirming my expectation that the defaults are > to remain unchanged for now, and I will thus proceed under this > assumption. > If we add default multilibs for you, then to be fair, we need to add default multilibs for other people that ask, and before long we are trying to build hundreds or maybe even thousands of multilibs by default which is unworkable. There are simply too many different extensions, and too many different valid combinations of them. A problem that is quickly getting worse, as there are a slew of extensions that are planned for final approval this year. The current set was defined before I started doing RISC-V work over 3 years ago, and I've been saying no to everyone that wants to change the default set. The current set is tractable for newbies to try to build and use. People that want a different set can define their own, and we have made it easy for people to define their own sets of multilibs as Kito pointed out. I do think that when the architecture profiles are adopted and implemented it would make sense to add them to the default set, and maybe eventually replace the default set. Jim