public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/29631] [4.1 regression] bug with promoted induction variable Date: Tue, 31 Oct 2006 23:34:00 -0000 [thread overview] Message-ID: <20061031233414.6135.qmail@sourceware.org> (raw) In-Reply-To: <bug-29631-2744@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from ebotcazou at gcc dot gnu dot org 2006-10-31 23:34 ------- Subject: Bug 29631 Author: ebotcazou Date: Tue Oct 31 23:34:05 2006 New Revision: 118346 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=118346 Log: PR rtl-optimization/29631 * loop.c (basic_induction_var): Add new parameter inner_mode. <PLUS>: If set, convert the increment to it before sign-extending. <CONST_INT>: Likewise. <SUBREG>: Set it. <ASHIFTRT>: Likewise. Return 0 if flag_wrapv. Added: branches/gcc-4_1-branch/gcc/testsuite/gcc.c-torture/execute/20061031-1.c Modified: branches/gcc-4_1-branch/gcc/ChangeLog branches/gcc-4_1-branch/gcc/loop.c branches/gcc-4_1-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29631
next prev parent reply other threads:[~2006-10-31 23:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-28 23:02 [Bug tree-optimization/29631] New: [4.1 regression] Incorrect zero extension of signed short IV falk at debian dot org 2006-10-28 23:05 ` [Bug middle-end/29631] " pinskia at gcc dot gnu dot org 2006-10-28 23:13 ` falk at debian dot org 2006-10-28 23:19 ` [Bug rtl-optimization/29631] " pinskia at gcc dot gnu dot org 2006-10-29 11:35 ` ebotcazou at gcc dot gnu dot org 2006-10-29 11:35 ` ebotcazou at gcc dot gnu dot org 2006-10-29 21:40 ` ebotcazou at gcc dot gnu dot org 2006-10-31 23:34 ` ebotcazou at gcc dot gnu dot org [this message] 2006-10-31 23:38 ` [Bug rtl-optimization/29631] [4.1 regression] bug with promoted induction variable ebotcazou at gcc dot gnu dot 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=20061031233414.6135.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).