RFC: x86_64-pc-mingw64 and getting it mapped out

I've created myself a local source bakery for GCC, binutils and
friends getting ready to think about providing 64bit toolsets.  I am
currently attempting --host=i686-pc-mingw32 --build=i686-pc-mingw32
--target=x86_64-pc-mingw64 builds.  Thinking about things like dwarf2
vs sjlj, threading models of win32, pthreads and seh and the bitness
of 32bit or 64bit I am considering being specific and creating
"triplet" strings similar to i686-pc-mingw-dwarf2win32,
x86_64-pc-mingw-sjljpthreads, etc.  This allows for
/mingw/i686-pc-mingw-dwarf2win32/lib,
/mingw/x86_64-pc-mingw-sjljpthreads/lib, etc to contain the disparate
libraries.  Also, which of these should we consider for our default
/mingw/lib directory?  Notice in this request I'm dropping the 32 and
64 indicators allowing the i686 and x86_64 to make the distinction of
bitness.

Any thoughts?

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev