public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Chen Gang <xili_gchen_5257@hotmail.com>, realmz6@gmail.com
Cc: adi-buildroot-devel@lists.sourceforge.net,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blackfin: Makefile: Skip reloc overflow issue when COMPILE_TEST enabled
Date: Wed, 08 Apr 2015 23:10:04 +0200	[thread overview]
Message-ID: <5525992C.6090906@nod.at> (raw)
In-Reply-To: <BLU437-SMTP520E6FA6915DA666F1AAA1B9FC0@phx.gbl>

Am 08.04.2015 um 23:05 schrieb Chen Gang:
> l1_text is at L1_CODE_START (e.g. for bf533, 0xff800000). If the kernel
> is too big, it may be overwritten, the related issue:
> 
>     LD      init/built-in.o
>   init/built-in.o: In function `do_early_param':
>   init/main.c:(.init.text+0xe0): relocation truncated to fit: R_BFIN_PCREL24 against symbol `strcmp' defined in .l1.text section in arch/blackfin/lib/lib.a(strcmp.o)
>   init/main.c:(.init.text+0x10e): relocation truncated to fit: R_BFIN_PCREL24 against symbol `strcmp' defined in .l1.text section in arch/blackfin/lib/lib.a(strcmp.o)
>   init/built-in.o: In function `unknown_bootoption':
> 
> blackfin is for embedded system, the size limitition is acceptable, so
> it is not the real world issue, which should be skipped if COMPILE_TEST
> enabled.

You're again papering over the real issue.
COMPILE_TEST is only one way to generate a too big kernel.
The right thing is to blow up and warn the user.

Thanks,
//richard

  reply	other threads:[~2015-04-08 21:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 21:05 [PATCH] blackfin: Makefile: Skip reloc overflow issue when COMPILE_TEST enabled Chen Gang
2015-04-08 21:10 ` Richard Weinberger [this message]
2015-04-08 21:16   ` Chen Gang
2015-04-08 21:19     ` Richard Weinberger
2015-04-09 13:15       ` Chen Gang
  -- strict thread matches above, loose matches on Subject: below --
2015-04-08 21:07 Chen Gang
2015-04-08 21:05 Chen Gang
2015-04-08 21:03 Chen Gang
2015-04-08 21:10 ` Chen Gang
2015-04-08 21:12   ` Richard Weinberger
2015-04-09 13:28     ` Chen Gang
2015-04-09 13:38       ` Richard Weinberger
2015-04-09 23:14         ` Chen Gang
2015-04-22  9:00 ` Steven Miao
2015-04-22 14:32   ` Chen Gang
2015-04-23  2:51     ` Steven Miao
2015-04-23 14:30       ` Chen Gang
2015-04-24  8:20         ` Steven Miao
2015-04-24 14:28           ` Chen Gang
     [not found] ` <5525994D.6090901@hotmail.com>
2015-07-01 15:31   ` Chen Gang
2015-07-01 15:36   ` Chen Gang

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=5525992C.6090906@nod.at \
    --to=richard@nod.at \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=realmz6@gmail.com \
    --cc=xili_gchen_5257@hotmail.com \
    /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