From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23331 invoked by alias); 30 Dec 2014 13:26:58 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 23255 invoked by uid 48); 30 Dec 2014 13:26:54 -0000 From: "hjl.tools at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-12/txt/msg02937.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D64412 --- Comment #14 from H.J. Lu --- (In reply to Uro=C5=A1 Bizjak from comment #13) > (In reply to H.J. Lu from comment #12) > > Created attachment 34361 [details] > > A new patch > >=20 > > Please try the new patch. >=20 > 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; >=20 > extern char G[8]; >=20 > char *a (size_t z) > { > return &G[z]; > } > --cut here-- >=20 > Without -fpic, the compiler expands to: >=20 > 6: {r90:DI=3Dr89:DI+`G';clobber flags:CC;} >=20 > Compare this with -fpic expansion: >=20 > 6: r92:DI=3D[const(unspec[`G'] 2)] > 7: r91:DI=3Dr92:DI > REG_EQUAL `G' > 8: {r90:DI=3Dr89:DI+r91:DI;clobber flags:CC;} >=20 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=3Dgeneric -march=3Dx86-= 64 -auxbase x -version -fPIC -o x.s GNU C11 (GCC) version 5.0.0 20141228 (experimental) (x86_64-unknown-linux-g= nu) 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=3D30 --param ggc-min-heapsize=3D4096 GNU C11 (GCC) version 5.0.0 20141228 (experimental) (x86_64-unknown-linux-g= nu) 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=3D30 --param ggc-min-heapsize=3D4096 Compiler executable checksum: e92c7e019abbedeeeac36edef3dbfdca Breakpoint 6, legitimize_pic_address (orig=3D0x7ffff19c8840, reg=3D0x0) at /export/gnu/import/git/gcc/gcc/config/i386/i386.c:13565 13565 rtx addr =3D orig; (gdb) bt #0 legitimize_pic_address (orig=3D0x7ffff19c8840, reg=3D0x0) at /export/gnu/import/git/gcc/gcc/config/i386/i386.c:13565 #1 0x0000000001082cf2 in ix86_expand_move (mode=3DDImode,=20 operands=3D0x7fffffffc840) at /export/gnu/import/git/gcc/gcc/config/i386/i386.c:17311 #2 0x00000000011a2c3f in gen_movdi (operand0=3D0x7ffff19c88b8,=20 operand1=3D0x7ffff19c8840) at /export/gnu/import/git/gcc/gcc/config/i386/i386.md:1938 #3 0x000000000084471f in insn_gen_fn::operator() ( this=3D0x1a82330 , a0=3D0x7ffff19c88b8, a1=3D0x7ffff1= 9c8840) at /export/gnu/import/git/gcc/gcc/recog.h:303 #4 0x000000000091cb20 in emit_move_insn_1 (x=3D0x7ffff19c88b8, y=3D0x7ffff= 19c8840) at /export/gnu/import/git/gcc/gcc/expr.c:3529 #5 0x000000000091cf74 in emit_move_insn (x=3D0x7ffff19c88b8, y=3D0x7ffff19= c8840) at /export/gnu/import/git/gcc/gcc/expr.c:3624 ... (gdb) call debug_rtx (orig) (symbol_ref:DI ("G") [flags 0x40] ) (gdb) >>From gcc-bugs-return-471931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 30 13:41:02 2014 Return-Path: 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: List-Archive: List-Post: List-Help: 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" 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: In-Reply-To: References: 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?id=64443 --- Comment #1 from Andrew Pinski --- >This commit seems to be breaking libstdc++-v3 runs on AArch64. Is this under Linux or with newlib?