2013/6/15 dw <[email protected]>:
> My responses:
>
> - While I don't really see the benefit, I'm ok with putting the inline
> implementations in their own .h file.  And it's going to feel odd
> putting an include at the *bottom* of a file.

Well, I see advantage exactly in the point of having the ability to
reuse implementation in header for the static-library.  So we have
implementation just at one place.

> - While duplicating the work (and adding an additional .c file) is a
> pain, having the implementations in two places (even the ones MS says
> can only be inline) is ok with me.

See above,  we don't need to maintain implementation at two places, if
we do things right.

> - Since there isn't any way to stop people from doing it, people can put
> intrinsic prototypes into their own files if they want to.  Of course
> unlike MSVC, they will only get the static library versions not the
> inlines without intrin.h.

Agreed.

> - Putting intrinsic prototypes in *system headers* (other than intrin.h)
> seems like a bad idea.  Without including intrin.h, any code that uses
> it will end up using the library version instead of the inline version.

Hmm, in platform-headers we have some intrinsics (and specializations
for C++), which need to be there without having all other things
declared from intrin.h header.  Anyway my concerns aren't strong here.

> But perhaps most importantly:
> - I believe we should consider intrin.h the "right" definition for gcc's
> version of the MSVC intrinsics.  Anything that conflicts with it needs
> to be changed.

Hmm, depends on the intrinsics ... in general yes.

> If we agree on these points, I'll send another email laying out the
> specific changes I want to make.  If that looks good, I'll start work on
> a patch.
>
> dw

Kai

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

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to