public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools 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 13:26:00 -0000 [thread overview] Message-ID: <bug-64412-4-E4eme2Vk4l@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 #14 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Uroš Bizjak from comment #13) > (In reply to H.J. Lu from comment #12) > > Created attachment 34361 [details] > > A new patch > > > > Please try the new patch. > > No, this approach is wrong. ix86_fixup_binary_operands should not be used to > legitimize PIC address. The -fpic expansion is already wrong, since it > produces: > --cut here-- > typedef __SIZE_TYPE__ size_t; > > extern char G[8]; > > char *a (size_t z) > { > return &G[z]; > } > --cut here-- > > Without -fpic, the compiler expands to: > > 6: {r90:DI=r89:DI+`G';clobber flags:CC;} > > Compare this with -fpic expansion: > > 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;} > This is generated in the backend: Starting program: /export/build/gnu/gcc/build-x86_64-linux/gcc/cc1 -fpreprocessed /tmp/x.i -quiet -dumpbase x.i -mtune=generic -march=x86-64 -auxbase x -version -fPIC -o x.s GNU C11 (GCC) version 5.0.0 20141228 (experimental) (x86_64-unknown-linux-gnu) compiled by GNU C version 4.8.3 20140911 (Red Hat 4.8.3-7), GMP version 5.1.2, MPFR version 3.1.2, MPC version 1.0.1 GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 GNU C11 (GCC) version 5.0.0 20141228 (experimental) (x86_64-unknown-linux-gnu) compiled by GNU C version 4.8.3 20140911 (Red Hat 4.8.3-7), GMP version 5.1.2, MPFR version 3.1.2, MPC version 1.0.1 GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 Compiler executable checksum: e92c7e019abbedeeeac36edef3dbfdca Breakpoint 6, legitimize_pic_address (orig=0x7ffff19c8840, reg=0x0) at /export/gnu/import/git/gcc/gcc/config/i386/i386.c:13565 13565 rtx addr = orig; (gdb) bt #0 legitimize_pic_address (orig=0x7ffff19c8840, reg=0x0) at /export/gnu/import/git/gcc/gcc/config/i386/i386.c:13565 #1 0x0000000001082cf2 in ix86_expand_move (mode=DImode, operands=0x7fffffffc840) at /export/gnu/import/git/gcc/gcc/config/i386/i386.c:17311 #2 0x00000000011a2c3f in gen_movdi (operand0=0x7ffff19c88b8, operand1=0x7ffff19c8840) at /export/gnu/import/git/gcc/gcc/config/i386/i386.md:1938 #3 0x000000000084471f in insn_gen_fn::operator() ( this=0x1a82330 <insn_data+201136>, a0=0x7ffff19c88b8, a1=0x7ffff19c8840) at /export/gnu/import/git/gcc/gcc/recog.h:303 #4 0x000000000091cb20 in emit_move_insn_1 (x=0x7ffff19c88b8, y=0x7ffff19c8840) at /export/gnu/import/git/gcc/gcc/expr.c:3529 #5 0x000000000091cf74 in emit_move_insn (x=0x7ffff19c88b8, y=0x7ffff19c8840) at /export/gnu/import/git/gcc/gcc/expr.c:3624 ... (gdb) call debug_rtx (orig) (symbol_ref:DI ("G") [flags 0x40] <var_decl 0x7ffff189e900 G>) (gdb) >From gcc-bugs-return-471931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 30 13:41:02 2014 Return-Path: <gcc-bugs-return-471931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29385 invoked by alias); 30 Dec 2014 13:41: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 29364 invoked by uid 48); 30 Dec 2014 13:40:58 -0000 From: "pinskia 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 13:41: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: pinskia 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-7qbsFfq2Bv@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/msg02938.txt.bz2 Content-length: 221 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd443 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- >This commit seems to be breaking libstdc++-v3 runs on AArch64. Is this under Linux or with newlib?
next prev parent reply other threads:[~2014-12-30 13:26 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 [this message] 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 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-E4eme2Vk4l@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: linkBe 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).