[LLVMdev] Arm Target
Bob Wilson
bob.wilson at apple.com
Mon Dec 6 22:23:46 PST 2010
On Dec 6, 2010, at 10:09 PM, ankur jain wrote:
> Thanx bob .
> We have been facing problem in memory allocation related stuff.
> If we start our application code using a memory allocation then things work fine.
> however without such explicit memory allocation that to a pointer which is never used ,our applcation crashes.
It is not very likely that this kind of problem is due to the compiler. I don't know what kind of system you are working with, but you'll need to find some other forum to get help with issues like this.
Sorry that I can't give you a better answer than that, but the symptoms you describe could be caused by any number of things, and none of them are likely to be related to LLVM.
> for your reference , the two case are as shown below :
> Case 1: Crash at a point when it tries to allocate memory in making an object of MyFrame in the code below.
> bool MyApp::OnInit()
> {
> if ( !wxApp::OnInit() )
> return false;
> // create the main application window
> MyFrame *frame = new MyFrame(_T("Minimal wxWidgets App"));
> frame->Show(true);
> return true;
> }
>
> Case 2: The code below is same as above except the first line in the function body and it runs fine .
> bool MyApp::OnInit()
> {
> char *ptr = new char[10000];
> if ( !wxApp::OnInit() )
> return false;
> // create the main application window
> MyFrame *frame = new MyFrame(_T("Minimal wxWidgets App"));
> frame->Show(true);
> return true;
> }
>
> I would like to know how using new makes a difference here ?
>
> On Tue, Dec 7, 2010 at 11:31 AM, Bob Wilson <bob.wilson at apple.com> wrote:
>
> On Dec 6, 2010, at 9:32 PM, ankur jain wrote:
>
> > Hello,
> >
> > We have been testing our llvm(2.8) compiled executables for arm target.
> > It seems as if the arm target support is not so stable/mature yet.
> > Is it so ?? We read about the same in the release notes but want a word from your side.
>
> The ARM target in LLVM is quite stable in 2.8. Can you provide more specific information about the kinds of problems you're seeing?
>
More information about the llvm-dev
mailing list