Declarations for the types used by Intel in the instrinsics guide?












2















Where are the declarations for the types used by the Intel intrinsic functions, according to the Intrinsics Guide?



For example, _mm_stream_si64 is defined as:



void _mm_stream_si64 (__int64* mem_addr, __int64 a)


However, after including <immintrin.h> on gcc on Linux, the type __int64 does not exist.






x86 intel sse intrinsics







share|improve this question


















  • 1





    GCC/clang's intrinsics are mostly compatible with ICC's documentation, but I think they don't provide that type. IIRC, they use a normal int64_t instead for the declaration of intrinsics that Intel defines with __int64.

    – Peter Cordes
    Nov 22 '18 at 20:23






  • 1





    @PeterCordes that was the first thing I tried, but int64_t doesn't work either, because mem_addr in that function is declared as long long *, and you can't convert int64_t * to that (at least you can't if your compiler is strict). So it seems hard to write portable code here...

    – BeeOnRope
    Nov 22 '18 at 21:28








  • 1





    Oops, I knew it was some standard type. Why can't you just use long long, then? Is it not alias-compatible with __int64 on ICC and/or MSVC? It's portably 64-bit on all compilers that support Intel intrinsics, in 32 and 64 bit mode. (64-bit movnti is only available in 64-bit mode, but possibly relevant for other intrinsics. Although usually the ones that can do 64-bit things in 32-bit mode use __m64)

    – Peter Cordes
    Nov 22 '18 at 21:45








  • 1





    @PeterCordes - yeah I guess I can just use long long (that's what I'm currently doing anyway). My concern was say that on Windows something like __int64 might be long int or whatever and then I'd have the reverse problem there. Of course it isn't, it seems to be long long there. It's a bit annoying you can't look at the guide and know what types to use though (why don't they just declare it as long long or at least define the types they use? seems Windows-centric).

    – BeeOnRope
    Nov 22 '18 at 22:05








  • 1





    Be careful with that; IIRC __int64 is the same as long on Windows and most Linux machines, but it's long long on macOS. The mismatch can cause some problems (for example, it bit me here). Basically the best thing you can do is just use the types Intel's (IMHO very poorly designed) API specifies, and cast as necessary so your API can use more reasonable types.

    – nemequ
    Nov 25 '18 at 6:24
















2















Where are the declarations for the types used by the Intel intrinsic functions, according to the Intrinsics Guide?



For example, _mm_stream_si64 is defined as:



void _mm_stream_si64 (__int64* mem_addr, __int64 a)


However, after including <immintrin.h> on gcc on Linux, the type __int64 does not exist.






x86 intel sse intrinsics







share|improve this question


















  • 1





    GCC/clang's intrinsics are mostly compatible with ICC's documentation, but I think they don't provide that type. IIRC, they use a normal int64_t instead for the declaration of intrinsics that Intel defines with __int64.

    – Peter Cordes
    Nov 22 '18 at 20:23






  • 1





    @PeterCordes that was the first thing I tried, but int64_t doesn't work either, because mem_addr in that function is declared as long long *, and you can't convert int64_t * to that (at least you can't if your compiler is strict). So it seems hard to write portable code here...

    – BeeOnRope
    Nov 22 '18 at 21:28








  • 1





    Oops, I knew it was some standard type. Why can't you just use long long, then? Is it not alias-compatible with __int64 on ICC and/or MSVC? It's portably 64-bit on all compilers that support Intel intrinsics, in 32 and 64 bit mode. (64-bit movnti is only available in 64-bit mode, but possibly relevant for other intrinsics. Although usually the ones that can do 64-bit things in 32-bit mode use __m64)

    – Peter Cordes
    Nov 22 '18 at 21:45








  • 1





    @PeterCordes - yeah I guess I can just use long long (that's what I'm currently doing anyway). My concern was say that on Windows something like __int64 might be long int or whatever and then I'd have the reverse problem there. Of course it isn't, it seems to be long long there. It's a bit annoying you can't look at the guide and know what types to use though (why don't they just declare it as long long or at least define the types they use? seems Windows-centric).

    – BeeOnRope
    Nov 22 '18 at 22:05








  • 1





    Be careful with that; IIRC __int64 is the same as long on Windows and most Linux machines, but it's long long on macOS. The mismatch can cause some problems (for example, it bit me here). Basically the best thing you can do is just use the types Intel's (IMHO very poorly designed) API specifies, and cast as necessary so your API can use more reasonable types.

    – nemequ
    Nov 25 '18 at 6:24














2












2








2








Where are the declarations for the types used by the Intel intrinsic functions, according to the Intrinsics Guide?



For example, _mm_stream_si64 is defined as:



void _mm_stream_si64 (__int64* mem_addr, __int64 a)


However, after including <immintrin.h> on gcc on Linux, the type __int64 does not exist.






x86 intel sse intrinsics







share|improve this question














Where are the declarations for the types used by the Intel intrinsic functions, according to the Intrinsics Guide?



For example, _mm_stream_si64 is defined as:



void _mm_stream_si64 (__int64* mem_addr, __int64 a)


However, after including <immintrin.h> on gcc on Linux, the type __int64 does not exist.






x86 intel sse intrinsics




x86 intel sse intrinsics






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 20:04









BeeOnRopeBeeOnRope

26.4k881180




26.4k881180








  • 1





    GCC/clang's intrinsics are mostly compatible with ICC's documentation, but I think they don't provide that type. IIRC, they use a normal int64_t instead for the declaration of intrinsics that Intel defines with __int64.

    – Peter Cordes
    Nov 22 '18 at 20:23






  • 1





    @PeterCordes that was the first thing I tried, but int64_t doesn't work either, because mem_addr in that function is declared as long long *, and you can't convert int64_t * to that (at least you can't if your compiler is strict). So it seems hard to write portable code here...

    – BeeOnRope
    Nov 22 '18 at 21:28








  • 1





    Oops, I knew it was some standard type. Why can't you just use long long, then? Is it not alias-compatible with __int64 on ICC and/or MSVC? It's portably 64-bit on all compilers that support Intel intrinsics, in 32 and 64 bit mode. (64-bit movnti is only available in 64-bit mode, but possibly relevant for other intrinsics. Although usually the ones that can do 64-bit things in 32-bit mode use __m64)

    – Peter Cordes
    Nov 22 '18 at 21:45








  • 1





    @PeterCordes - yeah I guess I can just use long long (that's what I'm currently doing anyway). My concern was say that on Windows something like __int64 might be long int or whatever and then I'd have the reverse problem there. Of course it isn't, it seems to be long long there. It's a bit annoying you can't look at the guide and know what types to use though (why don't they just declare it as long long or at least define the types they use? seems Windows-centric).

    – BeeOnRope
    Nov 22 '18 at 22:05








  • 1





    Be careful with that; IIRC __int64 is the same as long on Windows and most Linux machines, but it's long long on macOS. The mismatch can cause some problems (for example, it bit me here). Basically the best thing you can do is just use the types Intel's (IMHO very poorly designed) API specifies, and cast as necessary so your API can use more reasonable types.

    – nemequ
    Nov 25 '18 at 6:24














  • 1





    GCC/clang's intrinsics are mostly compatible with ICC's documentation, but I think they don't provide that type. IIRC, they use a normal int64_t instead for the declaration of intrinsics that Intel defines with __int64.

    – Peter Cordes
    Nov 22 '18 at 20:23






  • 1





    @PeterCordes that was the first thing I tried, but int64_t doesn't work either, because mem_addr in that function is declared as long long *, and you can't convert int64_t * to that (at least you can't if your compiler is strict). So it seems hard to write portable code here...

    – BeeOnRope
    Nov 22 '18 at 21:28








  • 1





    Oops, I knew it was some standard type. Why can't you just use long long, then? Is it not alias-compatible with __int64 on ICC and/or MSVC? It's portably 64-bit on all compilers that support Intel intrinsics, in 32 and 64 bit mode. (64-bit movnti is only available in 64-bit mode, but possibly relevant for other intrinsics. Although usually the ones that can do 64-bit things in 32-bit mode use __m64)

    – Peter Cordes
    Nov 22 '18 at 21:45








  • 1





    @PeterCordes - yeah I guess I can just use long long (that's what I'm currently doing anyway). My concern was say that on Windows something like __int64 might be long int or whatever and then I'd have the reverse problem there. Of course it isn't, it seems to be long long there. It's a bit annoying you can't look at the guide and know what types to use though (why don't they just declare it as long long or at least define the types they use? seems Windows-centric).

    – BeeOnRope
    Nov 22 '18 at 22:05








  • 1





    Be careful with that; IIRC __int64 is the same as long on Windows and most Linux machines, but it's long long on macOS. The mismatch can cause some problems (for example, it bit me here). Basically the best thing you can do is just use the types Intel's (IMHO very poorly designed) API specifies, and cast as necessary so your API can use more reasonable types.

    – nemequ
    Nov 25 '18 at 6:24








1




1





GCC/clang's intrinsics are mostly compatible with ICC's documentation, but I think they don't provide that type. IIRC, they use a normal int64_t instead for the declaration of intrinsics that Intel defines with __int64.

– Peter Cordes
Nov 22 '18 at 20:23





GCC/clang's intrinsics are mostly compatible with ICC's documentation, but I think they don't provide that type. IIRC, they use a normal int64_t instead for the declaration of intrinsics that Intel defines with __int64.

– Peter Cordes
Nov 22 '18 at 20:23




1




1





@PeterCordes that was the first thing I tried, but int64_t doesn't work either, because mem_addr in that function is declared as long long *, and you can't convert int64_t * to that (at least you can't if your compiler is strict). So it seems hard to write portable code here...

– BeeOnRope
Nov 22 '18 at 21:28







@PeterCordes that was the first thing I tried, but int64_t doesn't work either, because mem_addr in that function is declared as long long *, and you can't convert int64_t * to that (at least you can't if your compiler is strict). So it seems hard to write portable code here...

– BeeOnRope
Nov 22 '18 at 21:28






1




1





Oops, I knew it was some standard type. Why can't you just use long long, then? Is it not alias-compatible with __int64 on ICC and/or MSVC? It's portably 64-bit on all compilers that support Intel intrinsics, in 32 and 64 bit mode. (64-bit movnti is only available in 64-bit mode, but possibly relevant for other intrinsics. Although usually the ones that can do 64-bit things in 32-bit mode use __m64)

– Peter Cordes
Nov 22 '18 at 21:45







Oops, I knew it was some standard type. Why can't you just use long long, then? Is it not alias-compatible with __int64 on ICC and/or MSVC? It's portably 64-bit on all compilers that support Intel intrinsics, in 32 and 64 bit mode. (64-bit movnti is only available in 64-bit mode, but possibly relevant for other intrinsics. Although usually the ones that can do 64-bit things in 32-bit mode use __m64)

– Peter Cordes
Nov 22 '18 at 21:45






1




1





@PeterCordes - yeah I guess I can just use long long (that's what I'm currently doing anyway). My concern was say that on Windows something like __int64 might be long int or whatever and then I'd have the reverse problem there. Of course it isn't, it seems to be long long there. It's a bit annoying you can't look at the guide and know what types to use though (why don't they just declare it as long long or at least define the types they use? seems Windows-centric).

– BeeOnRope
Nov 22 '18 at 22:05







@PeterCordes - yeah I guess I can just use long long (that's what I'm currently doing anyway). My concern was say that on Windows something like __int64 might be long int or whatever and then I'd have the reverse problem there. Of course it isn't, it seems to be long long there. It's a bit annoying you can't look at the guide and know what types to use though (why don't they just declare it as long long or at least define the types they use? seems Windows-centric).

– BeeOnRope
Nov 22 '18 at 22:05






1




1





Be careful with that; IIRC __int64 is the same as long on Windows and most Linux machines, but it's long long on macOS. The mismatch can cause some problems (for example, it bit me here). Basically the best thing you can do is just use the types Intel's (IMHO very poorly designed) API specifies, and cast as necessary so your API can use more reasonable types.

– nemequ
Nov 25 '18 at 6:24





Be careful with that; IIRC __int64 is the same as long on Windows and most Linux machines, but it's long long on macOS. The mismatch can cause some problems (for example, it bit me here). Basically the best thing you can do is just use the types Intel's (IMHO very poorly designed) API specifies, and cast as necessary so your API can use more reasonable types.

– nemequ
Nov 25 '18 at 6:24












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437453%2fdeclarations-for-the-types-used-by-intel-in-the-instrinsics-guide%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437453%2fdeclarations-for-the-types-used-by-intel-in-the-instrinsics-guide%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

這個網誌中的熱門文章

Tangent Lines Diagram Along Smooth Curve

圖片
7 1 I am trying to replicate a diagram and have a minimal example. I don't know how to add additional tangents between the specified points and preserve smoothness. documentclass{article} usepackage{tikz} usetikzlibrary{calc,intersections} begin{document} begin{tikzpicture} % Axes draw [->, name path=x] (-1,0) -- (11,0) node [right] {$x$}; draw [->] (0,-1) -- (0,6) node [above] {$y$}; % Origin node at (0,0) [below left] {$0$}; % Points coordinate (start) at (1,-0.8); coordinate (c1) at (3,3); coordinate (c2) at (5.5,1.5); coordinate (c3) at (8,4); coordinate (end) at (10.5,-0.8); % show the points foreach n in {start,c1,c2,c3,end} fill [black] (n) circle (2pt) node [below] {}; % join the coordinates draw [thick,name path=curve] (start) to[out=70,in=180] (c1) to[out=0,in=180]
閱讀完整內容

Yusuf al-Mu'taman ibn Hud

圖片
Main article: Taifa of Zaragoza Al-Mu'taman Ruler of Zaragoza Reign 1081–1085 Predecessor Ahmad al-Muqtadir Successor Al-Mustain II Born Zaragoza Died 1085 Full name Yusuf ibn Ahmad al-Mu'taman ibn Hūd House Banu Hud Yusuf ibn Ahmad al-Mu'taman ibn Hūd (Arabic: المؤتمن بالله يوسف إبن أحمد إبن هود ‎, al-Mutaman bi l-Lah , died c. 1085) was the third king of the Banu Hud dynasty who ruled over the Taifa of Zaragoza from 1081 to 1085. Yusuf al-Mutaman reigned during the height of power of Muslim Zaragoza , following the thriving period of his father Ahmad al-Muqtadir. He continued his father's efforts and created around him a court of intellectuals, living in the beautiful palace of Aljafería, nicknamed as "the palace of joy". Al-Mu'taman was also a scholarly king and a patron of science, philosophy and arts. As an example of a wise king, he knew astrology, philosophy, and especially mathematics, a discipline in which
閱讀完整內容

Zucchini

圖片
This article is about the vegetable. For other uses, see Zucchini (disambiguation). Zucchini (courgette) A striped and a uniform color zucchini Genus Cucurbita Species Cucurbita pepo Origin 19th century northern Italy The zucchini ( / z uː ˈ k iː n i / , American English) or courgette ( / k ʊər ˈ ʒ ɛ t / , British English) is a summer squash which can reach nearly 1 metre (100 cm; 39 in) in length, but is usually harvested when still immature at about 15 to 25 cm (6 to 10 in). [1] A zucchini is a thin-skinned cultivar of what in Britain and Ireland is referred to as a marrow. [2] [3] In South Africa, a zucchini is known as a baby marrow. Along with certain other squashes and pumpkins, the zucchini belongs to the species Cucurbita pepo . It can be dark or light green. A related hybrid, the golden zucchini, is a deep yellow or orange color. [4] In a culinary context, the zucchini is treated as a vegetable; it is usually cooked and presented as a savory dish o
閱讀完整內容