LLVM ERROR: Cannot yet select: error - ios-simulator

Hello i am getting the following error when I am running my app in the simulator.
LLVM ERROR: Cannot yet select: ...
It seems that other have reported similar issues for the same combo:
* New sandy bridge MBP
* Iphone 4.3 Simulator
* opengl
Anyone have some clue?
Here is a short excerpt from the log:
LLVM ERROR: Cannot yet select: 0xa0237d8: v16i8 = bit_convert 0xa02aa48 [ORD=259] [ID=170]
0xa02aa48: v8i16 = X86ISD::PSHUFLW 0xa02a828, 0xa02a608 [ID=166]
0xa02a828: v8i16 = X86ISD::PSHUFHW 0xa0235b8, 0xa02a608 [ID=162]
0xa0235b8: v8i16 = llvm.x86.sse2.packssdw.128 0xa023530, 0xa0234a8, 0xa023420 [ORD=256] [ID=158]
0xa023530: i32 = Constant<647> [ORD=256] [ID=21]
0xa0234a8: v4i32 = bit_convert 0xa023310 [ORD=255] [ID=139]
0xa023310: v4f32 = llvm.x86.sse.cmp.ps 0xa023200, 0xa028d70, 0xb03c4e8, 0xa023288 [ORD=252] [ID=130]
0xa023200: i32 = Constant<784> [ORD=252] [ID=19]

I'm getting this same error. I just got the new sandy bridge MBP today, and on my previous computer, I do not have this problem.
Changing the target to iPad 4.2 instead of iPad 4.3 resolves the issue.
Here's how to change the target in the new version of Xcode:
http://developer.apple.com/library/mac/#documentation/IDEs/Conceptual/Xcode4TransitionGuide/Orientation/Orientation.html

I had the same Error on my MacBook Pro Intel Core i7 in the 4.3 simulator. I updated to Xcode 4.0.2 and now its working again.

This means that LLVM cannot do the instruction selection for some code. Usually this happens when you request some target-specific stuff in the code and disable the features via cmdline.
For example, if you'll use sse2 gcc intrinsics, but will compile for, say, i486, the same sort of message might occur (if not caught earlier by a frontend).
It's hard to say anything more definite without the full error line.

I had the same situation. It looks like a bug of LLVM 2.8 for the new sandy bridge. The work around is to use 4.2 simulator as NoEvilPeople said.
OpenGL apps exit in 4.3 Sim but work...
MacRuby build issues with LLVM
Attempt to force LLVM to treat sandy bridge as core2

In case this helps anyone, I was having the same problem too, but don't have the older SDK for the other fix here. Kazuki posted a link to a discussion over at Apple, and it looks like its a bug that a few people have reported, but that it has something to do with the simulator. That being said, the app I was having a problem with runs fine on-device for me, so that's another potential workaround while this is looked at more.

Related

QtCreator: Cannot run compiler 'g++'. Output:

I've installed the latest Qt through the online installer and with it installed the latest MinGW 64 bit compiler. I'm running windows 10 with the latest updates. Here is an error message upon opening one of the example projects:
Project ERROR: Cannot run compiler 'g++'. Output:
===================
# 1 "C:/Qt/5.14.1/mingw73_64/mkspecs/features/data/macros.cpp"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "C:/Qt/5.14.1/mingw73_64/mkspecs/features/data/macros.cpp"
QT_COMPILER_STDCXX = 201402L
# 26 "C:/Qt/5.14.1/mingw73_64/mkspecs/features/data/macros.cpp"
QMAKE_GCC_MAJOR_VERSION = 7
QMAKE_GCC_MINOR_VERSION = 3
QMAKE_GCC_PATCH_VERSION = 0
===================
Maybe you forgot to setup the environment?
Error while parsing file C:\Qt\Examples\Qt-5.14.1\widgets\itemviews\addressbook\addressbook.pro. Giving up.
Here is my kit and compiler setup:
I can confirm that C:\Qt\Tools\mingw730_64\bin\g++.exe exists, and C:\Qt\Tools\mingw730_64\bin is also added to PATH. I've tried the offline installer as well, with and without admin permissions but it didn't work. Everything seemingly looks fine (no red highlights or anything like that) so what is the problem here? Any help is appreciated.
Edit: I have a Ryzen 3 CPU, and from reading the qt forums there was a rare bug where Qt would fail to install without upgrading the BIOS. I updated mine and Qt installation went well. Just something that could be relevant.

how to resolve Appium bad parameters error

I am stuck at the error when the appium server shows error
[MJSONWP] Bad parameters: BadParametersError: Parameters were incorrect. We wanted {"required":["desiredCapabilities"],"optional":["requiredCapabilities","capabilities","sessionId","id"]} and you sent ["desiredCapabilities","requiredCapabilities","capabilities","alwaysMatch","firstMatch"]
In the eclipse it shows error
org.openqa.selenium.SessionNotCreatedException: Unable to create new remote session. desired capabilities = Capabilities [{app=C:\Users\Admin\workspace\Sling_App\src\app-dev-debug.apk}], required capabilities = Capabilities [{}]
I have been using 5.0.0 and also 4.1.2 client jar
Tried with Selenium 3 , 3.3
Appium Server I tried on are 1.6.2 , 1.6.3 and latest 1.6.4
Nothing Solves the problem ,
I read most of the articles related to this , but of no use
Please tell if any 1 has found solution to thisenter image description here
In ideal case we need to pass 6 capabilities(for APK testing) as below,
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability("deviceName","ANDROID");
capabilities.setCapability("platformVersion", "5.1");
capabilities.setCapability("platformName",Constant.appPlatform);
capabilities.setCapability("app", app.getAbsolutePath());
capabilities.setCapability("appPackage", Constant.appPackage);
capabilities.setCapability("appActivity",Constant.appActivity);
Also initiate appium webdriver instead of Android as below,
AppiumDriver driver = new AndroidDriver(new URL("http://127.0.0.1:4727/wd/hub"), capabilities);
I am using appium 1.6.4 and java client 4.12 with selenium stand alone 2.53.1.
AppPackage/AppActivity are required for simulator also.
Hope this helps you.
Thanks.

pyside qt4.8 os x core profile/3.2 compatibility (yes, I've read the other posts)

No matter what I've tried, I cannot get a proper 3.2 context in pyside using qt 4.8. I have triple checked via the gl extensions manager, and my computer is certainly capable (100% of 4.1 core features).
"simple" version doesn't work...
f = QGLFormat()
f.setProfile(QGLFormat.CoreProfile)
f.setVersion(3,2)
QGLFormat.setDefaultFormat(f)
In fact, I cannot even successfully create a glcontext...
class GLView(QGLWidget):
def __init__(self,name,parent=None):
QGLWidget.__init__(self,parent)
c = QGLContext(QGLFormat())
logger.critical(c.create()) #returns False
This is after a QApplication exists and a MainWindow class is created and shown...
If I try to set the format on the built-in QGLWidget context, it fails as well --
self.context().setFormat(f)
self.context().makeCurrent()
"Cannot make invalid context current". Similarly does not work even if coreprofile is not specified, and version is set at 2.1.
Moving any of these to the initializeGL callback makes no difference.
I've looked at the following questions, which have not resolved my issue
PyQt4 OpenGL: Enabling OpenGL Core Profile - solution was to move to qt5 (no official pyside release for this yet)
PyOpenGL cannot compile shader - on debian, does not have same problem as os x
Getting OpenGL context newer than 2.1 with Qt 4 and Mavericks - unresolved
Qt & OpenGL OS X: GLSL shader version only 120 on Mountain Lion - c++, same code does not work in pyside, as seen above
Any help on this would be greatly appreciated.
Thanks,
K

Linking issue with (Intel SDK) OpenCL and Code::Blocks

I was trying to get my problem solved for hours, but I did not find any usefull hints. Hopefully you guys can help me out:
Some usefull data:
OS: Windows 8 Basic 64bit
Library: Intel OpenCL SDK
Compiler: MinGW(-gcc) (latest version)
IDE: Code::Blocks (latest version)
Minimal not working Code:
#include <stdlib.h>
#include <CL/cl.h>
int main(void)
{
cl_uint available;
cl_platform_id* platforms = (cl_platform_id*)malloc(sizeof(cl_platform_id));
cl_int result = clGetPlatformIDs(1, platforms, &available);
free(platforms);
if(result == CL_SUCCESS)
return 0;
return -1;
}
Code::Blocks Global Compiler Settings:
Linker Settings: Added path to Intel's OpenCL.lib ([...]\Intel\OpenCL SDK\3.0\lib\x64\OpenCL.lib) (tried -lOpenCL as Other Options as well)
Search-Directories for Compiler: Path to Intels OpenCL-SDK include directory ([...]\Intel\OpenCL SDK\3.0\include)
Search-Directories for Linker: Path to Intels OpenCL-Lib directory ([...]\Intel\OpenCL SDK\3.0\lib\x64)
Build-Log:
mingw32-g++.exe -L"[...]\Intel\OpenCL SDK\3.0\lib\x64" -o bin\Release\openCLTest.exe obj\Release\main.o -s "[...]\Intel\OpenCL SDK\3.0\lib\x64\OpenCL.lib"
obj\Release\main.o:main.c:(.text.startup+0x39): undefined reference to `clGetPlatformIDs#12'
collect2.exe: error: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 0 seconds)
1 errors, 0 warnings (0 minutes, 0 seconds)
I do not know why he does not link properly.
The [...] in the text is modified by me to shorten the path, normally it would be "C:\Program Files (x86)...".
Hopefully you guys can help me! It is really frustrating! :(
Do you need more information?
EDIT:
Okay... one additional hour and I solved my own problem.
Hope this hint can help some other ppl:
I had to link additionally against the x86-library (seems that some functions are not implemented in X64).
Good to know -.-'''
I got the same problem and I tried hard to figure out the solution and finally I did :)
First of all my hardware are Intel Processor Intel(R) Core(TM) i5-2500 CPU # 3.30GHz and Intel(R) HD Graphics then I installed Intel OpenCL SDK 1.2 after updating the drivers. After that I configure the code::blocks to the new paths for include folder and lib folder as mentioned on the following link: http://www.obellianne.fr/alexandre/tutorials/OpenCL/tuto_opencl_codeblocks.php
Then I tried to compile the examples and I got linking problem as follows:
opencl.o(.text+0x6f):opencl.c: undefined reference to `clGetPlatformIDs#12'
opencl.o(.text+0xa7):opencl.c: undefined reference to `clGetDeviceIDs#24'
opencl.o(.text+0x142):opencl.c: undefined reference to `clGetDeviceInfo#20'
opencl.o(.text+0x263):opencl.c: undefined reference to `clGetDeviceInfo#20'
collect2: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 0 seconds)
4 errors, 0 warnings (0 minutes, 0 seconds)
I tried to use command line and I got the same error then I tried to uninstall Intel sdk and replace it with AMD sdk 2.8 which is support X86 CPU with SSE (Streaming SIMD Extension which is designed by Intel ) 2.x orlater
http://developer.amd.com/tools-and-sdks/heterogeneous-computing/amd-accelerated-parallel-processing-app-sdk/system-requirements-driver-compatibility/
Finally it works :)
I hope you find this comment useful.
According to an external source i stumbled upon along my own path of enlightenment to this problem i found out something is actually wrong with the mingw-w64 linker. mingw-w64's ld.exe does not want to link with the standard libopencl.a.. whether this is intel SDK specific or not im not sure but here is the link to the solution.
http://sourceforge.net/p/mingw-w64/support-requests/46/
you just have to link to the supplied libopencl.a instead of the default one.
still dont know exactly why the linker gives a problem but i have verified that the solution does (some how) solve the problem.

Phonegap IOS Running HiWorld Sample App Produces "EXC_BAD_ACCESS"

OSX: 10.6.8
Xcode: 4.0.2
Phonegap: 1.4.1.js or Cardova-1.7.0
Following simple HiWorld example http://phonegap.com/start produces the following error from:
AppDelegate.m:
self.viewCOntroller = [[[MainViewCOntroller alloc] init] autorelease];
ERROR:
Thread 1: Program received signal: "EXC_BAD_ACCESS"
EDIT: I was using the ipad 3.2 Simulator, as soon as I changed it to iphone 4.0 or above the problem went away.
This is (in my opinion), the most common error in iOs development.
The error means that you're trying to access something that has already been released.
You may be trying to access the viewController sometime after having already released it.
Remove autorelease and see what happens.

Resources