Andrew Pinski wrote: > I actually think the problems with 1 (b) are artificial and should not > be taken into account.
This is not a hypothetical or artificial issue -- as I said, all three problems I listed have been encountered by real users. > I actually depend on a common sysroot already > and it allows > me to do development of a newer compiler much faster and it allows some > of our game > developers to be able to test a new compiler without having another copy of > the SDK installed. Yes, that's clever. But, you can create a symbolic link to the sysroot from each installation with a single command. And, your installer for third-party developers can do that for you. > 1(a) is not confusing at all, if people read the documentation like they > should > be doing, it should be clear to them that it looks at both locations. Most developers do not start by reading the entire compiler manual -- especially including information about building the compiler itself. The typical software developer probably doesn't have any idea what the "configure-time prefix for the compiler" might even mean. Their knowledge of compilers is probably that -c, -D, -I, -g, and -O2 are useful command-line options. And, if using an IDE, maybe not even that! And, there's no reason they should need more information than that; there's no reason compiler users should have to have any knowldege about how the compiler is put together. > For 1(c), it is not going to slow it down that much, in fact it just one > or two extra Sorry, this is just incorrect. It's a significant issued (as much as 25% for some projects) as measured by actual customers in the field. > play but that is a miss-configuration of their systems at that point and > not really a GCC issue and should not be treated as such. A large class of users (most corporate developers, for example) run on systems they don't administer. We want the compiler to perform well on their systems, if possible. Even developers who do administer their own systems may not be expert administrators; I used to administer my own GNU/Linux box, but I didn't know about most of the options to the kernel or other parts of the system. And, many GCC users are running on Windows, where they have less control. -- Mark Mitchell CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x713
