From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: sfr@canb.auug.org.au, starvik@axis.com, jespern@axis.com,
netdev@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, linux-cris-kernel@axis.com,
jhs@mojatatu.com
Subject: Re: linux-next: Tree for Oct 6
Date: Wed, 7 Oct 2015 12:40:46 +0530 [thread overview]
Message-ID: <20151007071046.GA21158@sudip-pc> (raw)
In-Reply-To: <201510061446.t96EkrVV012371@ignucius.se.axis.com>
On Tue, Oct 06, 2015 at 04:46:53PM +0200, Hans-Peter Nilsson wrote:
> > From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> > Date: Tue, 6 Oct 2015 14:33:46 +0200
>
> > On Tue, Oct 06, 2015 at 06:25:22PM +1100, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20151002:
> >
> > The build for cris allmodconfig is failing with the error:
> >
> > net/sched/sch_dsmark.c: In function 'dsmark_dequeue':
> > net/sched/sch_dsmark.c:316:1: error: unrecognizable insn:
> > (insn 245 244 119 15 (set (reg:QI 11 r11 [179])
> > (and:QI (mem/s/j:QI (reg/f:SI 2 r2 [orig:48 D.44939 ] [48]) [0 D.44939_34->mask+0 S1 A8])
> > (reg:QI 11 r11 [179]))) include/net/dsfield.h:33 -1
> > (nil))
> > net/sched/sch_dsmark.c:316:1: internal compiler error: in extract_insn, at recog.c:2109
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <http://gcc.gnu.org/bugs.html> for instructions.
> > make[2]: *** [net/sched/sch_dsmark.o] Error 1
> > make[1]: *** [net/sched] Error 2
> > make[1]: *** Waiting for unfinished jobs....
> >
> > It says compiler error, but with 4.3-rc4 it compiled properly.
> > Build log of v4.3-rc4 is at
> > https://travis-ci.org/sudipm-mukherjee/parport/jobs/83633972
> >
> > Build log of linux-next is at:
> > https://travis-ci.org/sudipm-mukherjee/parport/jobs/83839470
>
> Thanks for the heads-up, but any chance of a bug report as per
> the instructions in the message? It'll only speed up matters.
I can try, but since I am using 4.6.3 version I doubt if I will get the
required response (Happened with another arch). And this is the latest
cris cross-compiler available in
https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/
BTW, I did a bisect and if I revert 47bbbb30b433 ("sch_dsmark: improve memory locality")
it again builds without any error.
regards
sudip
next prev parent reply other threads:[~2015-10-07 7:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 7:25 linux-next: Tree for Oct 6 Stephen Rothwell
2015-10-06 11:20 ` [PATCH] pwm: bcm7038: fix build failure Sudip Mukherjee
2015-10-06 11:20 ` Sudip Mukherjee
2015-10-06 12:33 ` linux-next: Tree for Oct 6 Sudip Mukherjee
2015-10-06 13:24 ` David Miller
2015-10-06 14:46 ` Hans-Peter Nilsson
2015-10-07 7:10 ` Sudip Mukherjee [this message]
2015-10-07 13:31 ` Hans-Peter Nilsson
-- strict thread matches above, loose matches on Subject: below --
2025-10-06 12:38 Mark Brown
2023-10-06 4:38 Stephen Rothwell
2022-10-06 7:38 Stephen Rothwell
2021-10-06 7:56 Stephen Rothwell
2020-10-06 12:12 Stephen Rothwell
2016-10-06 3:23 Stephen Rothwell
2011-10-06 6:28 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=20151007071046.GA21158@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=davem@davemloft.net \
--cc=hans-peter.nilsson@axis.com \
--cc=jespern@axis.com \
--cc=jhs@mojatatu.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=starvik@axis.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 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.