linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: <linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Build regressions/improvements in v3.7-rc5
Date: Mon, 12 Nov 2012 15:51:06 -0600	[thread overview]
Message-ID: <1352757066.32153.5@snotra> (raw)
In-Reply-To: <CAMuHMdXE0yJNivpirGgx08zqLH2086ydeOU6zswXj-+zn8OsWQ@mail.gmail.com> (from geert@linux-m68k.org on Mon Nov 12 15:02:46 2012)

On 11/12/2012 03:02:46 PM, Geert Uytterhoeven wrote:
> On Mon, Nov 12, 2012 at 9:58 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > JFYI, when comparing v3.7-rc5 to v3.7-rc4[3], the summaries are:
> >   - build errors: +14/-4
> 
> 14 regressions:
>   + drivers/virt/fsl_hypervisor.c: error: 'MSR_GS' undeclared (first
> use in this function):  => 799:93

These reports would be more useful if the actual .config were provided,  
rather than just saying "powerpc randconfig".

I doubt this particular one is a regression; it looks like the  
dependencies have always been too weak (patch sent) and you're just  
comparing different randomly-generated configs.

> powerpc-randconfig
> 
>   + error: relocation truncated to fit: R_PPC64_REL24 against symbol
> `._mcount' defined in .text section in arch/powerpc/kernel/entry_64.o:
> (.text+0x1ff9eb8) => (.text+0x1ffa274), (.text+0x1ff7840)
> 
> powerpc-allyesconfig

It's been over 3 years since powerpc-allyesconfig built (it's just too  
big for the relocation model the kernel uses) -- how is this a  
regression?

-Scott

  reply	other threads:[~2012-11-12 21:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 20:58 Build regressions/improvements in v3.7-rc5 Geert Uytterhoeven
2012-11-12 21:02 ` Geert Uytterhoeven
2012-11-12 21:51   ` Scott Wood [this message]
2012-11-13 10:39     ` Geert Uytterhoeven
2012-11-12 22:05   ` Stephen Rothwell

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=1352757066.32153.5@snotra \
    --to=scottwood@freescale.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 NNTP newsgroup(s).