All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Dennis Newbold <dennisn@pe.net>
Cc: linux-mips@linux-mips.org
Subject: Re: GCC generating wrong assembly code?
Date: Sat, 26 Oct 2002 05:18:44 +0200	[thread overview]
Message-ID: <20021026051844.B9509@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1021025110042.28181A-101000@shell1>; from dennisn@pe.net on Fri, Oct 25, 2002 at 11:30:36AM -0700

On Fri, Oct 25, 2002 at 11:30:36AM -0700, Dennis Newbold wrote:

>      I'm trying to build gcj (GNU Java ahead-of-time compiler) from
> the sources.  It ran for quite awhile, and then on a particular file,
> it got about 20 "Error: branch out of range" errors from the gas
> assembler.  I'm hoping that someone on this list that understands gcc

This is supposedly fixed in the very latest versions.

As a temporary workaround that works for most files enable optimization
-O or even -O2 for those files affected by this problem.  -fno-inline
or -Os may also help - basically everything that reduces the code size.

  Ralf

      parent reply	other threads:[~2002-10-26  3:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 18:30 GCC generating wrong assembly code? Dennis Newbold
2002-10-25 21:05 ` H. J. Lu
2002-10-26  3:18 ` Ralf Baechle [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=20021026051844.B9509@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=dennisn@pe.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.