All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Branch out of range issues
Date: Wed, 2 Jul 2008 14:17:20 +0100	[thread overview]
Message-ID: <20080702131720.GC15896@linux-mips.org> (raw)

Recently a few people have reported "branch out of range" problems building
recent kernels.  One way to fix those - at the risk of causing considerable
collateral damage - is using -ffunction-sections.  I'm hessitating to make
a change like this so short before a kernel release since at this point I'm
not convinved that this is actually needed.  Anyway I'd appreciate feedback
on the problem.

Thanks,

  Ralf

                 reply	other threads:[~2008-07-02 13:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080702131720.GC15896@linux-mips.org \
    --to=ralf@linux-mips.org \
    --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.