This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Andrew Pinski wrote:$0.02 from a user - I routinely use the MinGW gcc stuff, mostly the Ada compiler, in a production environment where I work. I'd love to see i686-mingw32 get more attention.On Wed, 2006-09-20 at 23:11 -0400, Mark Mitchell wrote:Reactions?
Change powerpc-unknown-linux-gnu to powerpc64-unknown-linux-gnu so that
we also require the 64bit of PowerPC to work.
To be clear, you're suggesting that we say "powerpc64-unknown-linux-gnu", but mean that both it's 32-bit and 64-bit modes should work?
That makes sense to me. What about MIPS/MIPS64?
Also move powerpc64-unknown-linux-gnu or powerpc-linux-gnu to Primary if powerpc-aix is moving to secondary so we keep a PowerPC up as a primary target.
Definitely; I'd confused myself.
5. Add i686-mingw32 as a secondary platform.
Is i686-pc-cygwin just as important as mingw32 then?
I wonder if you mean to ask whether mingw32 is as important as Cygwin, or the other way around?
I think both are important, and about equally so. Cygwin is widely used by people used to GNU software when running on Windows and has a very active community. Windows (without Cygwin) is of course a widely-used operating system, and my perception is that a reasonable number of people are using GCC to build non-Cygwin Windows applications. However, I have no hard data.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |