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/67716] [5] [SH]: Miscompiles libraw: Assembler: unaligned opcodes detected in executable segment Date: Tue, 29 Sep 2015 22:02:00 -0000 [thread overview] Message-ID: <bug-67716-4-cYvFkiZdwi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67716-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67716 --- Comment #20 from Kazumoto Kojima <kkojima at gcc dot gnu.org> --- (In reply to Oleg Endo from comment #19) I have no objection. I thought that the fix for PR67723 on trunk is first, though either way will be fine.
next prev parent reply other threads:[~2015-09-29 22:02 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-25 8:40 [Bug target/67716] New: " glaubitz at physik dot fu-berlin.de 2015-09-25 13:05 ` [Bug target/67716] " kkojima at gcc dot gnu.org 2015-09-25 16:38 ` glaubitz at physik dot fu-berlin.de 2015-09-25 16:40 ` glaubitz at physik dot fu-berlin.de 2015-09-25 16:41 ` glaubitz at physik dot fu-berlin.de 2015-09-25 16:41 ` glaubitz at physik dot fu-berlin.de 2015-09-25 16:43 ` glaubitz at physik dot fu-berlin.de 2015-09-26 6:33 ` olegendo at gcc dot gnu.org 2015-09-26 6:50 ` olegendo at gcc dot gnu.org 2015-09-26 8:39 ` kkojima at gcc dot gnu.org 2015-09-26 9:25 ` olegendo at gcc dot gnu.org 2015-09-26 12:11 ` kkojima at gcc dot gnu.org 2015-09-26 13:17 ` olegendo at gcc dot gnu.org 2015-09-26 13:30 ` kkojima at gcc dot gnu.org 2015-09-26 14:34 ` olegendo at gcc dot gnu.org 2015-09-26 22:28 ` kkojima at gcc dot gnu.org 2015-09-28 14:19 ` olegendo at gcc dot gnu.org 2015-09-29 5:36 ` kkojima at gcc dot gnu.org 2015-09-29 5:37 ` kkojima at gcc dot gnu.org 2015-09-29 13:37 ` olegendo at gcc dot gnu.org 2015-09-29 22:02 ` kkojima at gcc dot gnu.org [this message] 2015-10-03 15:21 ` olegendo at gcc dot gnu.org 2015-10-26 12:19 ` 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-67716-4-cYvFkiZdwi@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).