Ignoring 'target specific option mismatch' on inline

相关文章推荐

潇洒的雪糕 · 62. ...· 3 月前 ·

奔跑的骆驼 · Malware Development ...· 3 月前 ·

沉着的生菜 · MySQL数据类型 - JSON数据类型 ...· 3 年前 ·

大气的开心果 · excelhome论坛之家-掘金· 3 年前 ·

千年单身的冲锋衣 · 当打开从svn签出的安卓项目时，错误 ...· 3 年前 ·

风流倜傥的杨桃 · 如何在Wix中从不同的集合中复制表格？· 3 年前 ·

威武的香菇 · python - How to print ...· 3 年前 ·

Previous message (by thread): SMPlayer.net

Next message (by thread): Ignoring 'target specific option mismatch' on inline

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] The idea is to instantiate function templates with optimized SIMD routines multiple times, then I can compile all my code with -march=i386, and select the best implementation at runtime. However, after already spending a lot of time restructuring my code around this idea, I discover that gcc refuses to compile this without having the corresponding target options enabled: error: inlining failed in call to 'always_inline' '__m64 _mm_unpacklo_pi8(__m64, __m64)': target specific option mismatch That makes no sense to me. I want gcc to emit those SIMD instructions verbatim in my code, regardless of what compiler options the user specified. What then is the point of feature-test macros (__SSE__, etc)? I don't get it. Is there any option or attribute I can use to make gcc ignore these target option mismatches when inlining? Or any other way to make this work?

Previous message (by thread): SMPlayer.net

Next message (by thread): Ignoring 'target specific option mismatch' on inline

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

推荐文章

潇洒的雪糕 · 62. [SQL]SQLLineage解析SQL血缘 — Code-Cookbook 0.2 文档

3 月前

奔跑的骆驼 · Malware Development with Detours Library | Mohamed Alzhrani

3 月前

沉着的生菜 · MySQL数据类型 - JSON数据类型（2） - 墨天轮

3 年前

大气的开心果 · excelhome论坛之家-掘金

3 年前

千年单身的冲锋衣 · 当打开从svn签出的安卓项目时，错误 "不能使用subversion命令行客户端：svn"。

3 年前

风流倜傥的杨桃 · 如何在Wix中从不同的集合中复制表格？

3 年前

威武的香菇 · python - How to print a file to stdout? - Stack Overflow

3 年前