public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fthain at telegraphics dot com.au" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46179] Codegen/TLS: invalid assembler syntax
Date: Thu, 28 Oct 2010 15:34:00 -0000	[thread overview]
Message-ID: <20101028153400.wX9t_rOxwfEyqs3k-oIy38BjYrouCR_kwmFWbc8-5EY@z> (raw)
In-Reply-To: <bug-46179-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46179

--- Comment #7 from Finn Thain <fthain at telegraphics dot com.au> 2010-10-28 15:34:06 UTC ---
On Sun, 24 Oct 2010, Andreas Schwab wrote:

> This should habe [sic] been fixed up by m68k_final_prescan_insn.

(In reply to comment #4)
> The invalid address is generated by output_move_double.

Hmm. I think Andreas is dropping hints...

Is anyone able to regression test this patch for ColdFire? It seems to fix the
680x0 test cases.


  parent reply	other threads:[~2010-10-28 15:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  3:33 [Bug target/46179] New: " fthain at telegraphics dot com.au
2010-10-26 21:04 ` [Bug target/46179] " schwab@linux-m68k.org
2010-10-26 22:14 ` mkuvyrkov at gcc dot gnu.org
2010-10-27  0:47 ` fthain at telegraphics dot com.au
2010-10-27  8:41 ` schwab@linux-m68k.org
2010-10-27 13:28 ` fthain at telegraphics dot com.au
2010-10-28 15:21 ` fthain at telegraphics dot com.au
2010-10-28 15:34 ` fthain at telegraphics dot com.au [this message]
2010-11-01 16:08 ` tg at mirbsd dot org
2010-11-04 13:12 ` mkuvyrkov at gcc dot gnu.org
2010-11-04 16:27 ` tg at mirbsd dot org
2010-12-12 14:04 ` schwab at gcc dot gnu.org
2010-12-12 14:09 ` schwab@linux-m68k.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=20101028153400.wX9t_rOxwfEyqs3k-oIy38BjYrouCR_kwmFWbc8-5EY@z \
    --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: link
Be 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).