public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/52481] m68k-*: internal compiler error: in extract_insn, at recog.c:2123 Date: Mon, 05 Mar 2012 18:58:00 -0000 [thread overview] Message-ID: <bug-52481-4-K57qw6VDuj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52481-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52481 --- Comment #6 from Richard Henderson <rth at gcc dot gnu.org> 2012-03-05 18:57:40 UTC --- Author: rth Date: Mon Mar 5 18:57:36 2012 New Revision: 184952 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184952 Log: PR target/52481 * config/m68k/sync.md (atomic_test_and_set): Use expand_simple_unop instead of calling negqi2 directly. Modified: trunk/gcc/ChangeLog
prev parent reply other threads:[~2012-03-05 18:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-04 17:22 [Bug c++/52481] New: " ralf_corsepius at rtems dot org 2012-03-04 19:25 ` [Bug target/52481] " schwab@linux-m68k.org 2012-03-04 21:02 ` mikpe at it dot uu.se 2012-03-05 16:28 ` rth at gcc dot gnu.org 2012-03-05 18:38 ` rth at gcc dot gnu.org 2012-03-05 18:42 ` rth at gcc dot gnu.org 2012-03-05 18:46 ` rth at gcc dot gnu.org 2012-03-05 18:58 ` rth 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-52481-4-K57qw6VDuj@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).