public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lamshuyin at netvigator dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/18314] New: Abnormal behavior in optimization Date: Fri, 05 Nov 2004 23:57:00 -0000 [thread overview] Message-ID: <20041105235700.18314.lamshuyin@netvigator.com> (raw) For this program, -O2 will create an infinite loop: int test=0; void main(void) { while((volatile int)test!=0); } If "volatile int" is not allowed, there should be at least some warning or error, but it compiles successfully. -- Summary: Abnormal behavior in optimization Product: gcc Version: 3.4.2 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: lamshuyin at netvigator dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i386 GCC host triplet: i386 GCC target triplet: ARM http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18314
next reply other threads:[~2004-11-05 23:57 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-05 23:57 lamshuyin at netvigator dot com [this message] 2004-11-17 13:08 ` [Bug c/18314] " pinskia at gcc dot gnu dot org 2004-11-17 13:45 ` schwab at suse dot de 2004-11-17 15:46 ` pinskia 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=20041105235700.18314.lamshuyin@netvigator.com \ --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).