public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/54471] [4.8 Regression] FAIL: gcc.dg/sms-8.c execution test Date: Wed, 21 Nov 2012 17:19:00 -0000 [thread overview] Message-ID: <bug-54471-4-QvR0xUM2UB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54471-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54471 --- Comment #9 from Marc Glisse <glisse at gcc dot gnu.org> 2012-11-21 17:18:47 UTC --- Jakub, your patch makes sense to me (or min0.is_zero() and min1.is_zero()). I am ashamed I managed to get products with [0,n] (with n larger than MAX/2) wrong. Good thing Kenneth Zadeck's wide_int will soon allow us to remove most of this horrible code. Another test that shows the error (optimizes away the call to g): void g(); void h(); void f(unsigned __int128 x){ if(x>(unsigned __int128)(-3))return; unsigned __int128 y=2*x; if(y==42) g(); else h(); }
next prev parent reply other threads:[~2012-11-21 17:19 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-03 17:58 [Bug tree-optimization/54471] New: " danglin at gcc dot gnu.org 2012-09-19 12:08 ` [Bug tree-optimization/54471] " rguenth at gcc dot gnu.org 2012-11-20 12:06 ` jakub at gcc dot gnu.org 2012-11-21 2:27 ` dave.anglin at bell dot net 2012-11-21 13:02 ` danglin at gcc dot gnu.org 2012-11-21 13:03 ` danglin at gcc dot gnu.org 2012-11-21 13:14 ` danglin at gcc dot gnu.org 2012-11-21 13:37 ` jakub at gcc dot gnu.org 2012-11-21 13:56 ` jakub at gcc dot gnu.org 2012-11-21 14:42 ` jakub at gcc dot gnu.org 2012-11-21 17:19 ` glisse at gcc dot gnu.org [this message] 2012-11-21 17:32 ` jakub at gcc dot gnu.org 2012-11-26 9:20 ` jakub at gcc dot gnu.org 2012-11-26 9:26 ` jakub at gcc dot gnu.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-54471-4-QvR0xUM2UB@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).