This isn't really something that I see myself using for what is likely going to be a very long time, which is why I haven't commented on it so far, but I'm fairly certain there could be a big warning under any documentation for this flag concerning the runtime switching that Jon is worried about, something along the lines of USE AT YOUR OWN RISK all in bold letters while talking about the caveats, so that users know that this isn't something he/she can just do trivially during compilation
best regards, Julian On Sun, Dec 4, 2022 at 9:44 PM JonY via Mingw-w64-public < [email protected]> wrote: > On 12/4/22 12:48, LIU Hao wrote: > > 在 2022-12-04 20:16, Pali Rohár via Gcc 写道: > >> Hello! I would like to ask gcc people, what do you think about such > >> proposed -mcrtdll= parameter? > >> > >> There are lot of unofficial gcc patches which implement this -mcrtdll= > >> parameter and this parameter is present in more gcc forks. > >> So it looks like that this parameter is useful for more people. > >> > > > > I vote +1 for this in GCC 14. > > > > GCC 13 (i.e. current master branch) is at stage3 so it's not an option > > at this moment. > > I've been silent all this time because personally I'm rather ambivalent > about it. > > It will make users think they can just switch and jump to another > runtime without any downsides, only to hit a brick wall when they mix > them together, and then blame this as a GCC bug. Especially when they > try this with C++. > > > > > _______________________________________________ > Mingw-w64-public mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
