Hi, I'm using the latest xTimeComposer to try to write a program for the XC-1A board,
however whenever I try to build I now get the following error:
xcc1llvm: /build/swnb/autobuild/swrelease_enterprise_13/Centos32/build/sb/tools_llvm/src/lib/VMCore/Instructions.cpp:274: void llvm::CallInst::init(llvm::Value*, llvm::ArrayRef, const llvm::Twine&): Assertion `(i >= FTy->getNumParams() || FTy->getParamType(i) == Args->getType()) && "Calling a function with a bad signature!"' failed.
Aborted
xmake[1]: *** [.build_Debug/src/Blur.xc.o] Error 1
xmake: *** [bin/Debug/Blur_Debug.xe] Error 2
This is particularly odd because I don't use Centos. I did however import the code from an older version of the program on a Centos machine; however I have created new projects and copied over all the code by hand and this still hasn't change anything, so that might be irrelevant.
My project includes one xc file with a number of macros, one c file (provided for me) and a c header.
The only reference to any error like this, that I can find, is a recent bug post about compiler errors with multi-dimensional array declaration.
I am right up against a deadline now and probably won't be able to check back at this until the 2nd, but if this post can flag a program bug to someone from XMOS then thats good and I will try to provide more details if asked.
I'm going to try eliminating bit of my project now and will post back if this yield any success.
Also another relevant point is that every time I open the project, after about 5 minutes, I am prompted to convert the launcher code because it is a pre 12.0 version; this seems very suspicious, because the prompt is repeating and presumable the code is not converting, but, because the problem persisted even when I hand copied the code to a new project, I have mostly ruled that out as a reason.
After trying my code on the windows version and getting the following error
**** Build of configuration Debug for project Blur ****
xmake CONFIG=Debug all
No modules used.
Compiling Blur.xc
Assertion failed: (i >= FTy->getNumParams() || FTy->getParamType(i) == Args->getType()) && "Calling a function with a bad signature!", file z:/buildslave/swnb/tools/win764_nightly_ent13/build/sb/tools_llvm/src/lib/VMCore/Instructions.cpp, line 274
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
xmake[1]: *** [.build_Debug/src/Blur.xc.o] Error 1
xmake: *** [bin/Debug/Blur_Debug.xe] Error 2
I have concluded that the issue is the the ide cannot correctly recognise debian linux builds or windows xp, the OSs I am using, this may be a bug introduced but the latest update or it may have originated from actions by the OS developers; either way it should hopefully be an easy bug to fix now it has been noticed.
I am changing the title to reflect my suspicions.
Suspected Internal compiler bug: faulty OS recognition
-
- New User
- Posts: 2
- Joined: Tue Aug 26, 2014 6:48 pm
-
- New User
- Posts: 2
- Joined: Tue Aug 26, 2014 6:48 pm
Another relevant point is that every time I open the project, after about 5 minutes, I get a prompt to convert the launcher because it is a pre 12.0 legacy version.The fact that this is repeating and not converting seems very relevant to the problem but, because the problem persisted when I hand copied the code to a new project, I have mostly ruled that out as a reason.
-
- Experienced Member
- Posts: 84
- Joined: Mon Jan 18, 2010 2:52 pm
This looks like a compiler bug to me. I'll make sure that this gets logged and looked at this end.
I think that the fact that you are seeing references to 'centos' is purely due to the fact that this
is the distribution we use to build the tools, and this is reflected in the path on our build machines.
The legacy launcher popup occurs when a pre 12.x workspace containing run/debug configurations
is opened in the latest tools, and is required because the lauch format has changed. If you allow it to do the conversion,
or create a new workspace, import your projects then recreate the run/debug configurations, then this
warning should not appear again. If it does, then this looks like a bug, so it would be really good to be able to
reproduce this our end.
Hope this helps,
Cheers,
Kris.
I think that the fact that you are seeing references to 'centos' is purely due to the fact that this
is the distribution we use to build the tools, and this is reflected in the path on our build machines.
The legacy launcher popup occurs when a pre 12.x workspace containing run/debug configurations
is opened in the latest tools, and is required because the lauch format has changed. If you allow it to do the conversion,
or create a new workspace, import your projects then recreate the run/debug configurations, then this
warning should not appear again. If it does, then this looks like a bug, so it would be really good to be able to
reproduce this our end.
Hope this helps,
Cheers,
Kris.