public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rwahl at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/57229] New: 4.6/4.7/4.8 inconsistent check for PRE_MODIFY/POST_MODIFY in post_reload Date: Thu, 09 May 2013 14:09:00 -0000 [thread overview] Message-ID: <bug-57229-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57229 Bug ID: 57229 Summary: 4.6/4.7/4.8 inconsistent check for PRE_MODIFY/POST_MODIFY in post_reload Product: gcc Version: 4.6.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: rwahl at gmx dot de Created attachment 30077 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30077&action=edit Proposed fix. I have found an inconsistency in postreload.c: move2add_note_store(). While reload_combine_note_store() has been fixed to deal with PRE_MODIFY/POST_MODIFY in PR 47008 this change is missing for move2add_note_store(). This actually may lead to wrong code for the msp430 arch (which currently is not yet officially supported). But I think the code should be fixed anyway to avoid any surprise when some arch is triggering it. See the attached fix. This is the URL of the mspgcc bug report: https://sourceforge.net/p/mspgcc/bugs/353/
reply other threads:[~2013-05-09 14:09 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-57229-4@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).