public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "edwintorok at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/37868] New: code that doesn't breaks TBAA is misoptimized even with -fno-strict-aliasing Date: Sat, 18 Oct 2008 18:17:00 -0000 [thread overview] Message-ID: <bug-37868-15165@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1459 bytes --] +++ This bug was initially created as a clone of Bug #37867 +++ Cloning bug on Chris's request. Running gcc-4.3 -O2 on PR1386.c I get different results than with -O1. $ gcc-4.3 -O1 PR1386.c && ./a.out PR1386.c: In function main: PR1386.c:15: warning: large integer implicitly truncated to unsigned type PR1386.c:17: warning: large integer implicitly truncated to unsigned type bad bits: 0 $ gcc-4.3 -O2 PR1386.c && ./a.out PR1386.c: In function main: PR1386.c:15: warning: large integer implicitly truncated to unsigned type PR1386.c:17: warning: large integer implicitly truncated to unsigned type bad bits: fffffffffffffff0 $ g++-4.3 -O2 -fno-strict-aliasing x.c x.c: In function int main(): x.c:15: warning: large integer implicitly truncated to unsigned type x.c:17: warning: large integer implicitly truncated to unsigned type edwin@debian:~$ ./a.out bad bits: fffffffffffffff0 -- Summary: code that doesn't breaks TBAA is misoptimized even with -fno-strict-aliasing Product: gcc Version: 4.3.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: edwintorok at gmail dot com GCC build triplet: x86_64-linux-gnu GCC host triplet: x86_64-linux-gnu GCC target triplet: x86_64-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37868
next reply other threads:[~2008-10-18 18:17 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-18 18:17 edwintorok at gmail dot com [this message] 2008-10-18 18:30 ` [Bug tree-optimization/37868] code that " sabre at nondot dot org 2008-10-18 18:58 ` rguenth at gcc dot gnu dot org 2008-10-18 22:36 ` rguenth at gcc dot gnu dot org 2008-10-18 22:44 ` rguenth at gcc dot gnu dot org 2008-10-22 11:48 ` [Bug tree-optimization/37868] [4.3 Regression] " rguenth at gcc dot gnu dot org 2008-10-22 13:50 ` rguenth at gcc dot gnu dot org 2008-11-03 11:29 ` jakub at gcc dot gnu dot org 2008-11-07 12:51 ` rguenth at gcc dot gnu dot org 2008-11-20 12:14 ` rguenth at gcc dot gnu dot org 2008-11-20 12:15 ` rguenth at gcc dot gnu dot org 2008-11-20 12:28 ` rguenth 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=bug-37868-15165@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).