public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/24609] Same value duplicated in two different registers Date: Tue, 01 Nov 2005 14:54:00 -0000 [thread overview] Message-ID: <20051101145400.7483.qmail@sourceware.org> (raw) In-Reply-To: <bug-24609-1313@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from pinskia at gcc dot gnu dot org 2005-11-01 14:54 ------- Actually it is "int*" and "int" and that mainly comes down to how we repesent (int*)[d]; If we change the code (we should be able to do this in the IR also, Daniel Berlin had a patch which did it): extern int abs (int __x); extern int bar (short*, short, int); struct s { short int* top; short int* left; short int* diag; }; typedef int aar[]; typedef aar *aptr; typedef char par[]; typedef par *pptr; int foo (int *a, struct s* p, short int pv[6][16]) { int s = 0; int b; aptr a1; a1 = (aptr)(a); pptr p1= (pptr)(p); for (b = 0; b < 6; ++b) { int d; short int ps; if (abs (p->left[0] - p->diag[0]) < abs (p->diag[0] - p->top[0])) d = 1; else d = 2; (*a1)[b] = d; ps = (*p1)[d - 1]; s += bar (pv[b], ps, a[b]); } return s; } -- We get: .L12: movl $1, %eax xorl %edx, %edx ..... jl .L12 movl $2, %eax movl $1, %edx jmp .L5 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24609
next prev parent reply other threads:[~2005-11-01 14:54 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-01 5:33 [Bug tree-optimization/24609] New: " ian at airs dot com 2005-11-01 6:02 ` [Bug tree-optimization/24609] " ian at airs dot com 2005-11-01 14:54 ` pinskia at gcc dot gnu dot org [this message] 2005-11-01 16:09 ` ian at airs dot com 2005-11-01 16:17 ` pinskia at gcc dot gnu dot org 2005-11-01 18:06 ` ian at airs dot com 2005-11-01 18:46 ` ian at airs dot com 2005-11-01 18:47 ` [Bug tree-optimization/24609] [4.1 regression] " ian at airs dot com 2005-11-02 0:58 ` ian at airs dot com 2005-11-03 6:28 ` ian at airs dot com 2006-03-08 16:03 ` [Bug tree-optimization/24609] [4.1/4.2 " pinskia at gcc dot gnu dot org 2006-04-12 18:36 ` mmitchel at gcc dot gnu dot org 2006-04-27 12:36 ` rguenth at gcc dot gnu dot org 2006-05-25 2:40 ` mmitchel at gcc dot gnu dot org 2006-07-10 13:01 ` [Bug tree-optimization/24609] [4.0/4.1/4.2 " rguenth at gcc dot gnu dot org 2006-08-25 7:47 ` bonzini at gnu dot org 2006-08-25 7:48 ` bonzini at gnu dot org 2007-02-14 9:08 ` [Bug tree-optimization/24609] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org 2007-07-04 22:11 ` pinskia at gcc dot gnu dot org 2008-01-21 17:26 ` steven at gcc dot gnu dot org 2008-01-23 6:49 ` ian at airs dot com
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=20051101145400.7483.qmail@sourceware.org \ --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).