public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/53886] Seg fault in sh_insn_length_adjustment Date: Sun, 08 Jul 2012 13:41:00 -0000 [thread overview] Message-ID: <bug-53886-4-Bs4TrO7KxC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53886-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53886 --- Comment #5 from Kazumoto Kojima <kkojima at gcc dot gnu.org> 2012-07-08 13:41:09 UTC --- (In reply to comment #4) > The patch below fixes this particular crash, but I'm not sure whether it is > the right thing to do in this case. Looks fine to me except that the line >+ rtx prev,next,pat; requires space after comma.
next prev parent reply other threads:[~2012-07-08 13:41 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-07 16:41 [Bug target/53886] New: " rmansfield at qnx dot com 2012-07-08 11:33 ` [Bug target/53886] " olegendo at gcc dot gnu.org 2012-07-08 11:41 ` olegendo at gcc dot gnu.org 2012-07-08 11:52 ` rmansfield at qnx dot com 2012-07-08 12:19 ` olegendo at gcc dot gnu.org 2012-07-08 12:23 ` olegendo at gcc dot gnu.org 2012-07-08 13:41 ` kkojima at gcc dot gnu.org [this message] 2012-07-08 13:45 ` olegendo at gcc dot gnu.org 2012-07-08 13:59 ` kkojima at gcc dot gnu.org 2012-07-09 22:39 ` olegendo at gcc dot gnu.org 2012-07-10 22:08 ` olegendo at gcc dot gnu.org 2012-07-10 22:12 ` olegendo 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-53886-4-Bs4TrO7KxC@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).