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 target/47744] New: [x32] ICE: in reload_cse_simplify_operands, at postreload.c:403 Date: Tue, 15 Feb 2011 06:10:00 -0000 [thread overview] Message-ID: <bug-47744-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47744 Summary: [x32] ICE: in reload_cse_simplify_operands, at postreload.c:403 Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: hjl.tools@gmail.com On x32 branch, I got [hjl@gnu-6 ilp32-21]$ cat m.i typedef int int32_t; static const int init_jk[] = {2,3,4,6}; int __kernel_rem_pio2(double *x, double *y, int e0, int nx, int prec, const int32_t *ipio2) { int32_t jz,jx,jv,jp,jk,carry,n,iq[20],i,j,k,m,q0,ih; double z,fw,f[20],fq[20],q[20]; jk = init_jk[prec]; jp = jk; jx = nx-1; for (i=0;i<=jk;i++) { for(j=0,fw=0.0;j<=jx;j++) fw += x[j]*f[jx+i-j]; q[i] = fw; } for(i=0,j=jz,z=q[jz];j>0;i++,j--) { z = q[j-1]+fw; } n = (int32_t) z; return n&7; } [hjl@gnu-6 ilp32-21]$ make m.s /export/build/gnu/gcc-x32/build-x86_64-linux/gcc/xgcc -B/export/build/gnu/gcc-x32/build-x86_64-linux/gcc/ -S -o m.s -mx32 -std=gnu99 -O2 -fPIC m.i m.i: In function \u2018__kernel_rem_pio2\u2019: m.i:18:1: error: insn does not satisfy its constraints: (insn 108 106 186 3 (set (reg:SI 40 r11 [207]) (plus:SI (plus:SI (mult:SI (reg:SI 1 dx [205]) (const_int 8 [0x8])) (subreg:SI (plus:DI (reg/f:DI 7 sp) (const_int 208 [0xd0])) 0)) (const_int -160 [0xffffffffffffff60]))) m.i:3 251 {*lea_1_x32} (nil)) m.i:18:1: internal compiler error: in reload_cse_simplify_operands, at postreload.c:403 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. make: *** [m.s] Error 1 [hjl@gnu-6 ilp32-21]$
next reply other threads:[~2011-02-15 4:55 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-15 6:10 hjl.tools at gmail dot com [this message] 2011-02-15 6:30 ` [Bug target/47744] " hjl.tools at gmail dot com 2011-02-15 13:44 ` hjl at gcc dot gnu.org 2011-02-18 15:02 ` hjl.tools at gmail dot com 2011-02-18 19:38 ` hjl at gcc dot gnu.org 2011-03-01 17:27 ` hjl.tools at gmail dot com 2011-03-01 19:21 ` hjl at gcc dot gnu.org 2011-03-29 6:27 ` hjl.tools at gmail dot com 2011-04-02 5:31 ` hjl at gcc dot gnu.org 2011-04-02 5:50 ` hjl at gcc dot gnu.org 2011-07-17 17:26 ` ubizjak at gmail dot com 2011-07-17 17:27 ` ubizjak at gmail dot com 2011-07-17 18:29 ` hjl.tools at gmail dot com 2011-07-17 20:02 ` ubizjak at gmail dot com 2011-07-17 20:08 ` ubizjak at gmail dot com 2011-07-17 20:27 ` hjl.tools at gmail dot com 2011-07-17 21:14 ` ubizjak at gmail dot com 2011-07-17 21:21 ` hjl.tools at gmail dot com 2011-07-17 21:28 ` hjl.tools at gmail dot com 2011-07-17 22:04 ` ubizjak at gmail dot com 2011-07-17 22:12 ` hjl.tools at gmail dot com 2011-07-17 22:18 ` ubizjak at gmail dot com 2011-07-17 22:44 ` hjl.tools at gmail dot com 2011-07-17 22:48 ` ubizjak at gmail dot com 2011-07-17 22:55 ` hjl.tools at gmail dot com 2011-07-17 23:00 ` ubizjak at gmail dot com 2011-07-18 0:03 ` hjl.tools at gmail dot com 2011-07-18 4:18 ` hjl.tools at gmail dot com 2011-07-18 9:09 ` ubizjak at gmail dot com 2011-07-18 13:55 ` hjl.tools at gmail dot com 2011-07-18 14:01 ` ubizjak at gmail dot com 2011-07-18 14:04 ` hjl.tools at gmail dot com 2011-07-18 14:54 ` hjl.tools at gmail dot com 2011-07-18 16:54 ` ubizjak at gmail dot com 2011-07-18 16:56 ` hjl.tools at gmail dot com 2011-07-18 17:18 ` ubizjak at gmail dot com 2011-07-18 17:51 ` hjl at gcc dot gnu.org 2011-07-18 17:52 ` uros at gcc dot gnu.org 2011-07-18 17:54 ` hjl at gcc dot gnu.org 2011-07-18 18:30 ` ubizjak at gmail dot com 2011-08-03 14:08 ` hjl 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-47744-4@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).