public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/53386] Bad assembly code produced for m68000 Date: Thu, 17 May 2012 15:37:00 -0000 [thread overview] Message-ID: <bug-53386-4-DDL5P7CZN7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53386-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 Andreas Schwab <schwab@linux-m68k.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal --- Comment #11 from Andreas Schwab <schwab@linux-m68k.org> 2012-05-17 15:30:09 UTC --- I would be ok with changing linux.h to honor -mstrict-align, though m68k_return_in_memory would have to be left out. The default will of course continue to be -mno-strict-align.
next prev parent reply other threads:[~2012-05-17 15:30 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-17 4:05 [Bug target/53386] New: " ljalvs at gmail dot com 2012-05-17 8:46 ` [Bug target/53386] " schwab@linux-m68k.org 2012-05-17 10:19 ` ljalvs at gmail dot com 2012-05-17 10:30 ` ljalvs at gmail dot com 2012-05-17 11:00 ` mikpe at it dot uu.se 2012-05-17 11:09 ` ljalvs at gmail dot com 2012-05-17 11:32 ` mikpe at it dot uu.se 2012-05-17 12:06 ` mikpe at it dot uu.se 2012-05-17 13:01 ` mikpe at it dot uu.se 2012-05-17 14:40 ` ljalvs at gmail dot com 2012-05-17 15:11 ` mikpe at it dot uu.se 2012-05-17 15:37 ` schwab@linux-m68k.org [this message] 2012-05-17 15:56 ` ljalvs at gmail dot com 2012-05-18 17:37 ` ljalvs at gmail dot com 2015-01-19 22:49 ` law at redhat dot com
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-53386-4-DDL5P7CZN7@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).