public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/34592] useless computation found Date: Tue, 08 Jan 2008 17:56:00 -0000 [thread overview] Message-ID: <20080108172605.2470.qmail@sourceware.org> (raw) In-Reply-To: <bug-34592-9596@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from manu at gcc dot gnu dot org 2008-01-08 17:26 ------- (In reply to comment #3) > > I also counted about 300 similar cases where Intel > produced warning #593. I think there is quite a bit > of pointless computation going on. > Thanks. I think optimisers should remove all of them so they should not have any effect. Nonetheless, if they are not really used, they should be removed from the code. > I attach a patch again 4.3 snapshot 20071228. Unfortunately, GCC 4.3 is open only for regression and documentation fixes. Your patch would need to wait for GCC 4.4. Yet, you can submit it right now and there are chances that someone will review. To avoid conflicts between maintainer of different parts of the compiler, I would suggest one different submission per component (or if you cannot distinguish the components, one submission per file). > Hint: Perhaps if this patch gets into 4.3 it would encourage > me to look at the other 300 cases ? Patches must be bootstrapped+regression tested and sent to gcc-patches. Check http://gcc.gnu.org/contribute.html for further instructions. If you need help with a particular step, write me an email. Examples of submissions can be found in the archives of gcc-patches. -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34592
next prev parent reply other threads:[~2008-01-08 17:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-12-26 13:46 [Bug bootstrap/34592] New: " dcb314 at hotmail dot com 2007-12-26 14:01 ` [Bug bootstrap/34592] " pinskia at gcc dot gnu dot org 2008-01-03 22:02 ` [Bug other/34592] " dcb314 at hotmail dot com 2008-01-03 22:23 ` dcb314 at hotmail dot com 2008-01-04 9:33 ` aldot at gcc dot gnu dot org 2008-01-04 19:10 ` dcb314 at hotmail dot com 2008-01-08 17:56 ` manu at gcc dot gnu dot org [this message] 2010-05-06 10:59 ` manu 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=20080108172605.2470.qmail@sourceware.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).