public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bigotp at acm dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/47138] backport r158175: replace dominated uses in loop-invariant Date: Sun, 02 Jan 2011 18:33:00 -0000 [thread overview] Message-ID: <bug-47138-4-I5HBKCyWuD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47138-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47138 --- Comment #4 from Peter A. Bigot <bigotp at acm dot org> 2011-01-02 18:33:21 UTC --- Exactly: this problem also occurs with the TI msp430 target machine description, currently maintained as a fork on the mspgcc project on sourceforge. I don't know how to provide a test case other than a tar file and patch that adds that target, and a demonstration that without the referenced change build of libgcc fails with unrecognized instruction patterns (a parallel clobber didn't get updated, and the assert at the bottom of cfgrtl.c:patch_jump_insn gets hit when redirect_jump fails on a target that isn't an exit block). On further reflection, since this is fixed in trunk and the msp430 target wouldn't be back-ported into your repository for an existing release series, I'm ok with closing this as not-worth-fixing. I did, however, want an upstream problem report on which to hang the patches that I'll be maintaining.
next prev parent reply other threads:[~2011-01-02 18:33 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-31 23:55 [Bug rtl-optimization/47138] New: " bigotp at acm dot org 2011-01-01 8:47 ` [Bug rtl-optimization/47138] " ebotcazou at gcc dot gnu.org 2011-01-01 8:49 ` ebotcazou at gcc dot gnu.org 2011-01-02 17:50 ` rguenth at gcc dot gnu.org 2011-01-02 18:18 ` ebotcazou at gcc dot gnu.org 2011-01-02 18:33 ` bigotp at acm dot org [this message] 2011-01-03 8:05 ` ebotcazou 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-47138-4-I5HBKCyWuD@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).