public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/54386] [4.8 Regression] Unaligned mem load wrongly generated for inlined inline/static function Date: Mon, 04 Feb 2013 22:42:00 -0000 [thread overview] Message-ID: <bug-54386-4-gS2QGZr4Ig@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54386-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54386 --- Comment #15 from Oleg Endo <olegendo at gcc dot gnu.org> 2013-02-04 22:41:47 UTC --- Author: olegendo Date: Mon Feb 4 22:41:44 2013 New Revision: 195742 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=195742 Log: PR tree-optimization/54386 * gcc.target/sh/pr54386.c: New. Added: trunk/gcc/testsuite/gcc.target/sh/pr54386.c Modified: trunk/gcc/testsuite/ChangeLog
prev parent reply other threads:[~2013-02-04 22:42 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-27 19:05 [Bug middle-end/54386] New: " olegendo at gcc dot gnu.org 2012-09-06 14:50 ` [Bug middle-end/54386] " gjl at gcc dot gnu.org 2012-09-06 16:04 ` olegendo at gcc dot gnu.org 2012-10-29 20:38 ` olegendo at gcc dot gnu.org 2012-10-29 22:18 ` mikpe at it dot uu.se 2012-10-29 22:23 ` [Bug middle-end/54386] [4.8 Regression] " olegendo at gcc dot gnu.org 2012-10-30 9:05 ` olegendo at gcc dot gnu.org 2012-10-30 19:28 ` mikpe at it dot uu.se 2012-10-31 8:24 ` ebotcazou at gcc dot gnu.org 2012-11-27 20:47 ` [Bug tree-optimization/54386] " jamborm at gcc dot gnu.org 2012-11-30 16:12 ` jamborm at gcc dot gnu.org 2012-12-03 13:28 ` jamborm at gcc dot gnu.org 2012-12-03 13:29 ` jamborm at gcc dot gnu.org 2012-12-03 13:32 ` jamborm at gcc dot gnu.org 2012-12-04 9:53 ` olegendo at gcc dot gnu.org 2013-02-04 22:42 ` olegendo at gcc dot gnu.org [this message]
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-54386-4-gS2QGZr4Ig@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).