public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64412] [regression] ICE in offload compiler: in extract_insn, at recog.c:2327
Date: Tue, 30 Dec 2014 15:32:00 -0000	[thread overview]
Message-ID: <bug-64412-4-CB57kRCJFH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64412-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64412

--- Comment #17 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to H.J. Lu from comment #16)
> > > This is generated in the backend:
> > 
> > Yes, but the question is, why somehow similar testcase legitimizes the
> > address correctly with -fpic, while the original testcase doesn't.
> 
> My impressions are most of PIC addresses like:
> 
>     6: r92:DI=[const(unspec[`G'] 2)]
>     7: r91:DI=r92:DI
>       REG_EQUAL `G'
>     8: {r90:DI=r89:DI+r91:DI;clobber flags:CC;}
> 
> is generated by x86 backend vi ix86_expand_move and x86 backend was never
> presented with other opportunities before.  X86 backend isn't prepared to
> handle some RTL expansions from offload.

The x86 backend did survive many years just fine, so I think offload should be
fixed to follow approach that generic middle-end takes. The testcase I posted
expands without problems; in this case middle-end knows that symbol address has
to be moved to a register. It looks like offload bypasses generic expansion
functions (that would magically fix this issue).
>From gcc-bugs-return-471944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 30 15:34:02 2014
Return-Path: <gcc-bugs-return-471944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24427 invoked by alias); 30 Dec 2014 15:34:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24400 invoked by uid 48); 30 Dec 2014 15:33:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64443] New std::string implementation breaks tests on AArch64.
Date: Tue, 30 Dec 2014 15:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64443-4-fPMfnavwR9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64443-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64443-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-12/txt/msg02951.txt.bz2
Content-length: 214

https://gcc.gnu.org/bugzilla/show_bug.cgi?idd443

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Probably the same issue as PR 64368 so it's probably a problem with the non-gnu
clocale model.


  parent reply	other threads:[~2014-12-30 15:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 12:29 [Bug lto/64412] New: " iverbin at gcc dot gnu.org
2014-12-26 19:17 ` [Bug lto/64412] " hjl.tools at gmail dot com
2014-12-26 19:35 ` iverbin at gcc dot gnu.org
2014-12-27 15:21 ` [Bug target/64412] " hjl.tools at gmail dot com
2014-12-29 16:57 ` iverbin at gcc dot gnu.org
2014-12-29 16:57 ` iverbin at gcc dot gnu.org
2014-12-29 16:58 ` iverbin at gcc dot gnu.org
2014-12-29 18:10 ` hjl.tools at gmail dot com
2014-12-29 19:27 ` hjl.tools at gmail dot com
2014-12-29 19:28 ` hjl.tools at gmail dot com
2014-12-29 20:33 ` iverbin at gcc dot gnu.org
2014-12-29 20:33 ` iverbin at gcc dot gnu.org
2014-12-29 22:06 ` hjl.tools at gmail dot com
2014-12-30 13:09 ` [Bug middle-end/64412] " ubizjak at gmail dot com
2014-12-30 13:26 ` hjl.tools at gmail dot com
2014-12-30 14:35 ` ubizjak at gmail dot com
2014-12-30 15:12 ` hjl.tools at gmail dot com
2014-12-30 15:32 ` ubizjak at gmail dot com [this message]
2014-12-31 12:42 ` iverbin at gcc dot gnu.org
2015-01-08 16:04 ` iverbin at gcc dot gnu.org
2015-01-08 16:09 ` jakub at gcc dot gnu.org
2015-01-09 21:38 ` jakub at gcc dot gnu.org
2015-01-09 21:51 ` jakub at gcc dot gnu.org

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=bug-64412-4-CB57kRCJFH@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).