From: Dan Carpenter <dan.carpenter@oracle.com>
To: Vineet Gupta <vgupta@kernel.org>, lkp@intel.com
Cc: linux-snps-arc@lists.infradead.org,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
Claudiu Zissulescu <claziss@synopsys.com>
Subject: Re: [linux-next:master] BUILD REGRESSION 2a2aa3f05338270aecbe2492fda910d6c17e0102
Date: Thu, 7 Jul 2022 10:34:18 +0300 [thread overview]
Message-ID: <20220707073418.GE2316@kadam> (raw)
In-Reply-To: <416b7d42-51ec-2995-8f22-4d4c9ffe4624@kernel.org>
If I had to guess, I'd say it was probably the recent changes in
linux-next with bitops. Those things messed up Smatch as well and the
timing fits. But I don't have a way to test.
Anyway, let's ask the kbuild devs.
On Wed, Jul 06, 2022 at 11:09:13AM -0700, Vineet Gupta wrote:
>
>
> On 7/5/22 23:49, Dan Carpenter wrote:
> > [ trimmed massive CC list (see below) ]
> >
> > What's going on with all the arch/arc build breakage on linux-next?
> >
> > regards,
> > dan carpenter
>
> linux-snps-arc is not there, does one need to subscribe to these ?
I don't know how the CC list for BUILD REGRESSIONs is made.
> > > Unverified Error/Warning (likely false positive, please contact us if interested):
> > >
> > > block/partitions/efi.c:223:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
> > > block/sed-opal.c:427:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
> > > crypto/asymmetric_keys/pkcs7_verify.c:311:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
> > > drivers/ata/libata-core.c:2802:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
> > > drivers/ata/libata-eh.c:2842:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
> > > drivers/ata/sata_dwc_460ex.c:691:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
> > > drivers/base/power/runtime.c:1570:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
> > > drivers/block/rbd.c:6142:1: internal compiler error: in arc_ifcvt, at config/arc/arc.c:9637
>
> [snip..]
>
> We would need more specifics: what compiler version is this ?
> Thx for bringing this to our attention.
Hey LTP devs, which GCC are you using and which .config is generating
these "internal compiler error" issues?
regards,
dan carpenter
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2022-07-07 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 23:41 [linux-next:master] BUILD REGRESSION 2a2aa3f05338270aecbe2492fda910d6c17e0102 kernel test robot
2022-07-05 23:41 ` kernel test robot
2022-07-05 23:41 ` kernel test robot
2022-07-05 23:41 ` kernel test robot
2022-07-05 23:41 ` kernel test robot
2022-07-05 23:41 ` kernel test robot
2022-07-05 23:41 ` kernel test robot
2022-07-05 23:41 ` [Intel-wired-lan] " kernel test robot
2022-07-05 23:41 ` [dm-devel] " kernel test robot
2022-07-05 23:41 ` kernel test robot
2022-07-06 6:49 ` Dan Carpenter
2022-07-06 18:09 ` Vineet Gupta
2022-07-07 7:34 ` Dan Carpenter [this message]
2022-07-07 7:58 ` Chen, Rong A
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=20220707073418.GE2316@kadam \
--to=dan.carpenter@oracle.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=claziss@synopsys.com \
--cc=linux-snps-arc@lists.infradead.org \
--cc=lkp@intel.com \
--cc=vgupta@kernel.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.