linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Build regressions/improvements in v4.3-rc1
Date: Sun, 13 Sep 2015 18:32:28 -0700	[thread overview]
Message-ID: <55F623AC.4050408@roeck-us.net> (raw)
In-Reply-To: <20150913165758.GE21084@n2100.arm.linux.org.uk>

Russell,

On 09/13/2015 09:57 AM, Russell King - ARM Linux wrote:
> On Sun, Sep 13, 2015 at 08:19:26AM -0700, Guenter Roeck wrote:
>> arm:rpc_defconfig:
>>
>> fs/fat/dir.c: In function 'fat_ioctl_filldir':
>> fs/fat/dir.c:752:43: internal compiler error: Max. number of generated reload insns per insn is achieved (90)
>
> Not much can be done about that - gcc people aren't interested in fixing
> ARMv3 compiler support anymore, although this is still buildable with
> older compilers.  I don't see any point in removing the platform just
> because GCC has decided to break itself.
>
To be fair, they actually fixed a number of similar problems recently,
though I don't know if they happened to fix this one in later versions of gcc.
This specific error seems to be pretty far spread.

Guess you are saying that there is no plan to implement a workaround.
Fair enough; I'll just remove the configuration from my list of tests.

>> arm64:allmodconfig:
>>
>> drivers/firmware/qcom_scm-32.c:196:4: error: expected string literal before ‘__asmeq’
>> drivers/firmware/qcom_scm-32.c:221:2: error: implicit declaration of function ‘secure_flush_area’
>> drivers/firmware/qcom_scm-32.c:239:2: error: implicit declaration of function ‘outer_inv_range’
>> drivers/firmware/qcom_scm-32.c:331:4: error: expected string literal before ‘__asmeq’
>> drivers/firmware/qcom_scm-32.c:361:4: error: expected string literal before ‘__asmeq’
>
> This file shouldn't be built on ARM64, and there's a fix in the pipeline
> which obviously didn't make -rc1 for it.
>

Fixes are in the pipeline for most of the problems. Only exception is alpha;
the patches necessary to fix the problems there only met silence.

I'll probably wait for -rc4 or -rc5 and then send a pull request for everything
that is left directly to Linus.

Thanks,
Guenter

  reply	other threads:[~2015-09-14  1:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1442134868-17607-1-git-send-email-geert@linux-m68k.org>
2015-09-13  9:03 ` Build regressions/improvements in v4.3-rc1 Geert Uytterhoeven
2015-09-13 15:19   ` Guenter Roeck
2015-09-13 16:57     ` Russell King - ARM Linux
2015-09-14  1:32       ` Guenter Roeck [this message]
2015-09-13 20:23     ` Geert Uytterhoeven
2015-09-14  5:19       ` Michael Ellerman

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=55F623AC.4050408@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --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).