Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: ARC Fix conditional move contstraint.
Date: Tue, 30 Aug 2016 17:44:18 +0000	[thread overview]
Message-ID: <1472579057.10978.8.camel@synopsys.com> (raw)
In-Reply-To: <20160826225323.1a57ae0f@free-electrons.com>

Hi Thomas,

Looks like I tried to build it in a slightly different conditions.?
I reproduced that bug and hope our team will be able to fix the issue soon.

Thank you for your remarks.

-- 
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>

On Fri, 2016-08-26 at 22:53 +0200, Thomas Petazzoni wrote:
> Vlad, Alexey, Eugeniy,
> 
> On Fri, 26 Aug 2016 12:28:32 +0300, Vlad Zakharov wrote:
> > 
> > The patch solves one of the ARC internal compiler issues.
> > 
> > Fixes:
> > http://autobuild.buildroot.net/results/1c4/1c4493c6a18b7a93a0368420c8f79032f9330891//
> > http://autobuild.buildroot.net/results/510/51071b790866b0c7083de3a94ad2a427009096af//
> > http://autobuild.buildroot.net/results/09e/09e037c628ca2a27d8eb832dd070f50ec7ebb72a//
> FWIW, this last build issue is *not* fixed by this patch. This last
> build failure is on mesa3d, with:
> 
> main/get.c: In function '_mesa_GetBooleani_v':
> main/get.c:2320:1: error: insn does not satisfy its constraints:
> ?}
> ?^
> (insn 79 72 80 7 (set (reg/f:SI 147 virtual-stack-vars)
> ????????(reg:SI 2 r2)) main/get.c:2315 3 {*movsi_insn}
> ?????(nil))
> main/get.c:2320:1: internal compiler error: in extract_constrain_insn, at recog.c:2190
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://bugs.buildroot.net/> for instructions.
> 
> And the build result
> http://autobuild.buildroot.net/results/5cc/5ccb47e2af780982d71d924ef30008f16573ad73//build-end.log
> is the *exact* same failure, but at commit
> https://git.buildroot.net/buildroot/commit/?id=2567f6f2f34a1ecfc25604bf8bf93b8bc065fc63,
> which is *after* I committed and pushed your ARC fix (and the
> configuration was using the internal toolchain backend, so the
> toolchain was built from scratch).
> 
> Best regards,
> 
> Thomas

      reply	other threads:[~2016-08-30 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26  9:28 [Buildroot] [PATCH] gcc: ARC Fix conditional move contstraint Vlad Zakharov
2016-08-26 13:37 ` Thomas Petazzoni
2016-08-26 20:53 ` Thomas Petazzoni
2016-08-30 17:44   ` Vlad Zakharov [this message]

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=1472579057.10978.8.camel@synopsys.com \
    --to=vladislav.zakharov@synopsys.com \
    --cc=buildroot@busybox.net \
    /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