> A more specific question is - if I fix some Clang i686-pc-win32 > compatibility issue with MSVC for some language feature (e.g. > returning a struct), > should I make sure Clang i686-pc-mingw32 behavior is not changed by my > patches (a) > or should I make sure that Clang i686-pc-mingw32 generates > MSVC-compatible ABI for the same feature (b) > ?You need to make sure you won't break the compatibility with gcc on mingw. Regardless whether this is a) or b) -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
What if it's already broken? 2013/3/28 Anton Korobeynikov <asl at math.spbu.ru>:>> A more specific question is - if I fix some Clang i686-pc-win32 >> compatibility issue with MSVC for some language feature (e.g. >> returning a struct), >> should I make sure Clang i686-pc-mingw32 behavior is not changed by my >> patches (a) >> or should I make sure that Clang i686-pc-mingw32 generates >> MSVC-compatible ABI for the same feature (b) >> ? > You need to make sure you won't break the compatibility with gcc on > mingw. Regardless whether this is a) or b) > > -- > With best regards, Anton Korobeynikov > Faculty of Mathematics and Mechanics, Saint Petersburg State University
> What if it's already broken?You mean that clang on mingw32 is not compatible with gcc on mingw32? Then this is bug, please fill a PR. If your patch fixes it - then it's fine. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University