public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/20100] New: [4.0 regression] static call incorrectly judged constant, moved out of loop Date: Sun, 20 Feb 2005 15:15:00 -0000 [thread overview] Message-ID: <20050220030431.20100.hp@gcc.gnu.org> (raw) In the test-case to be attached and entered in gcc.c-torture/execute alt. gcc.dg/torture as prNNNNN-1.c, there's a call to get_n, which is moved out of the loop. This happens before rtl passes. The FC3-bundled gcc known as gcc-3.4.2-6.fc3 (for i686) does not have this bug. Trunk as of LAST_UPDATED "Sat Feb 19 00:34:51 UTC 2005" has this bug, apparent with cris-axis-elf and i686-pc-linux-gnu. -- Summary: [4.0 regression] static call incorrectly judged constant, moved out of loop Product: gcc Version: 4.0.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hp at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu, cris-axis-elf http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20100
next reply other threads:[~2005-02-20 3:04 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-20 15:15 hp at gcc dot gnu dot org [this message] 2005-02-20 15:21 ` [Bug tree-optimization/20100] " hp at gcc dot gnu dot org 2005-02-20 15:21 ` hp at gcc dot gnu dot org 2005-02-20 15:24 ` hp at gcc dot gnu dot org 2005-02-20 15:37 ` [Bug rtl-optimization/20100] " pinskia at gcc dot gnu dot org 2005-02-20 16:38 ` hp at gcc dot gnu dot org 2005-02-20 22:30 ` [Bug tree-optimization/20100] " pinskia at gcc dot gnu dot org 2005-02-20 22:32 ` pinskia at gcc dot gnu dot org 2005-02-20 22:33 ` pinskia at gcc dot gnu dot org 2005-02-21 2:21 ` [Bug tree-optimization/20100] [4.0 Regression] LIM is pulling out a pure function even though there is something which can modify global memory hp at gcc dot gnu dot org 2005-02-21 2:37 ` pinskia at gcc dot gnu dot org 2005-02-21 15:00 ` pinskia at gcc dot gnu dot org 2005-02-21 16:16 ` dnovillo at gcc dot gnu dot org 2005-02-23 12:50 ` cvs-commit at gcc dot gnu dot org 2005-02-23 15:21 ` steven at gcc dot gnu dot org 2005-02-23 15:29 ` steven at gcc dot gnu dot org 2005-02-24 12:14 ` cvs-commit 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=20050220030431.20100.hp@gcc.gnu.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).