public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/65028] [5 Regression] 450.soplex in SPEC CPU 2006 is miscompiled Date: Wed, 18 Feb 2015 22:18:00 -0000 [thread overview] Message-ID: <bug-65028-4-3fbj0mBb2B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65028-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65028 --- Comment #43 from Martin Jambor <jamborm at gcc dot gnu.org> --- (In reply to H.J. Lu from comment #42) > Does it skip a jump func when its argument alignment is unknown? No, I don't think it does. Cur is initialized to unknown alignment and then only overwrites the whole structure if alignment is known. > Shouldn't propagate_alignment_accross_jump_function keeps the > minimum argument alignment, not the maximum argument alignment? No, it does not calculate minimums or maximums at all. If it encounters a different value than one it has seen previously, the result is unknown alignment (this is what Honza thinks is just way too pessimistic and fixes with his attached patch). I really find it very suspicious that even the jump-function printing code, which is a an iteration over edges as simple as they get, does not see the wrong call. If it is originally an indirect call, then obviously initialization of the lattice is wrong because the cgraph_local_p information is wrong.
next prev parent reply other threads:[~2015-02-18 22:18 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-11 20:23 [Bug ipa/65028] New: " hjl.tools at gmail dot com 2015-02-11 20:32 ` [Bug ipa/65028] " hubicka at gcc dot gnu.org 2015-02-12 13:28 ` rguenth at gcc dot gnu.org 2015-02-12 13:41 ` jamborm at gcc dot gnu.org 2015-02-13 17:02 ` jamborm at gcc dot gnu.org 2015-02-13 19:03 ` hubicka at ucw dot cz 2015-02-13 20:05 ` hubicka at gcc dot gnu.org 2015-02-13 20:06 ` hubicka at gcc dot gnu.org 2015-02-13 20:31 ` hubicka at gcc dot gnu.org 2015-02-16 17:35 ` jamborm at gcc dot gnu.org 2015-02-16 17:42 ` hjl.tools at gmail dot com 2015-02-16 18:40 ` hubicka at gcc dot gnu.org 2015-02-16 19:44 ` hjl.tools at gmail dot com 2015-02-16 21:20 ` hubicka at ucw dot cz 2015-02-17 16:23 ` hjl.tools at gmail dot com 2015-02-17 16:41 ` hjl.tools at gmail dot com 2015-02-17 17:03 ` hjl.tools at gmail dot com 2015-02-17 18:07 ` hjl.tools at gmail dot com 2015-02-17 18:14 ` jamborm at gcc dot gnu.org 2015-02-17 18:16 ` hubicka at gcc dot gnu.org 2015-02-17 18:20 ` hjl.tools at gmail dot com 2015-02-17 18:32 ` hjl.tools at gmail dot com 2015-02-17 19:09 ` hjl.tools at gmail dot com 2015-02-17 19:41 ` hjl.tools at gmail dot com 2015-02-17 20:37 ` hjl.tools at gmail dot com 2015-02-17 21:27 ` hjl.tools at gmail dot com 2015-02-17 22:32 ` hjl.tools at gmail dot com 2015-02-17 22:33 ` hjl.tools at gmail dot com 2015-02-17 23:52 ` hjl.tools at gmail dot com 2015-02-17 23:54 ` hubicka at ucw dot cz 2015-02-18 17:13 ` hjl.tools at gmail dot com 2015-02-18 17:32 ` hjl.tools at gmail dot com 2015-02-18 19:33 ` hjl.tools at gmail dot com 2015-02-18 20:09 ` hjl.tools at gmail dot com 2015-02-18 20:19 ` hubicka at ucw dot cz 2015-02-18 21:16 ` hubicka at ucw dot cz 2015-02-18 21:21 ` hjl.tools at gmail dot com 2015-02-18 21:41 ` hubicka at ucw dot cz 2015-02-18 21:41 ` jamborm at gcc dot gnu.org 2015-02-18 21:54 ` hjl.tools at gmail dot com 2015-02-18 21:54 ` hjl.tools at gmail dot com 2015-02-18 22:18 ` jamborm at gcc dot gnu.org [this message] 2015-02-18 22:33 ` hjl.tools at gmail dot com 2015-02-18 22:34 ` hjl.tools at gmail dot com 2015-02-18 22:46 ` jamborm at gcc dot gnu.org 2015-02-18 23:11 ` hjl.tools at gmail dot com 2015-02-18 23:11 ` hjl.tools at gmail dot com 2015-02-19 16:36 ` trippels at gcc dot gnu.org 2015-02-19 16:41 ` jamborm at gcc dot gnu.org 2015-02-19 18:46 ` jamborm at gcc dot gnu.org 2015-02-19 19:03 ` jamborm at gcc dot gnu.org 2015-02-19 19:37 ` hjl.tools at gmail dot com 2015-02-19 19:57 ` hubicka at ucw dot cz 2015-02-19 20:06 ` hjl.tools at gmail dot com 2015-02-19 23:32 ` hubicka at gcc dot gnu.org 2015-02-20 6:46 ` hubicka at ucw dot cz 2015-02-20 10:12 ` trippels at gcc dot gnu.org 2015-02-20 13:43 ` jamborm 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-65028-4-3fbj0mBb2B@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).