> Could you please also prepare patch for crt's intrinsic-implementation > files? I've been pondering how to do this, both for the InterlockedOr functions and the __stos* functions. Duplicating the same code in two places goes against my nature. I figure the best answer would be to define the macros these use one time, then use the macros in both places. That way if anyone needed to change these functions again in the future, they'd only have to remember to do it in one place.
The question is: Where to put them? Including winnt.h in __stosb.c is a bad idea. __stosb.c already includes intrin.h, but winnt.h doesn't always include it. That leaves making a new include file (maybe intrnmac.h for intrinsic macros). I'm debating whether it's worth adding a new file for this. For just the 2 macros approved so far, perhaps not. However, I have more macros I'm going to be proposing as patches (8 total if they are all accepted). So, I can: 1) Just expand the macros and paste them into the crt files. 2) Add the intrnmac.h file, and modify winnt.h, __stos*.c, etc to use it. 3) Propose some of the other patches and see if they are accepted before doing either 1 or 2. I like #2, but #3 could be a cautious intermediate step. #1 is probably best if a release is imminent. Let me know how you'd like me to proceed. dw ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
