public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: ARM gcc help
Date: Wed, 10 Mar 2010 09:49:00 -0000	[thread overview]
Message-ID: <4B976B14.4080808@redhat.com> (raw)
In-Reply-To: <a9d632591003090115q32675e21oc5547dc5573ecbdc@mail.gmail.com>

On 03/09/2010 09:15 AM, Ruvinda Dhambarage wrote:
> hi,
> Iam using gcc 4.1.0 to compile code for a ARM922T.
> my code runs from the internal 64KB SRAM.
> when i run some functions it gets stuck or behaves unexpectedly when
> the .bin file gets larger than ~28KB.
> curiously, its the functions in the .o files that i added last that
> gets stuck. The functions in the .o which were added first, work
> without getting stuck.
> 
> what are the possible causes?

Bad hardware.  OS bug.  Linker bug.  You made a mistake somewhere that
corrupts memory. Etc, etc.

Andrew.

      reply	other threads:[~2010-03-10  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a9d632591003090053q63a9e362ke3dff2dfac643c2e@mail.gmail.com>
2010-03-09  9:15 ` Ruvinda Dhambarage
2010-03-10  9:49   ` Andrew Haley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B976B14.4080808@redhat.com \
    --to=aph@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).