Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Jerry Walden <jerry.walden@lantronix.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Gcc - can't branch to undefined symbol
Date: Thu, 29 Jan 2004 23:14:27 +0100	[thread overview]
Message-ID: <20040129221426.GA8465@linux-mips.org> (raw)
In-Reply-To: <603BA0CFF3788E46A0DB0918D9AA95100A0E3088@sj580004wcom.int.lantronix.com>

On Thu, Jan 29, 2004 at 12:25:16PM -0800, Jerry Walden wrote:

> I am using gcc 3.3.2 - when I assemble a file that has a branch to a
> label, and the label is not defined in the .S file (i.e. there is no
> extern - the label exists in another .S file) the error "cannot branch
> to an undefined symbol" results.  Using an older version of
> mipsel-gnu-linux-gcc does not report this error.  Any idea what I am
> doing wrong?

This construct is illegal because it cannot be represented in MIPS ELF.

  Ralf

  parent reply	other threads:[~2004-01-29 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 20:25 Gcc - can't branch to undefined symbol Jerry Walden
2004-01-29 20:25 ` Jerry Walden
2004-01-29 22:14 ` Ralf Baechle [this message]
2004-01-30  6:32   ` Thiemo Seufer

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=20040129221426.GA8465@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=jerry.walden@lantronix.com \
    --cc=linux-mips@linux-mips.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