http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46179
--- Comment #7 from Finn Thain 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_
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46179
--- Comment #6 from Finn Thain 2010-10-28
15:21:36 UTC ---
Created attachment 22191
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22191
possible fix
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46179
--- Comment #5 from Finn Thain 2010-10-27
13:28:01 UTC ---
> The invalid address is generated by output_move_double.
I have to say it, the .md files I looked at are hands-down the most complex and
baroque code I've ever seen. So I don't understa
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46179
--- Comment #3 from Finn Thain 2010-10-27
00:47:23 UTC ---
> Just to check that this is not a lingering issue from backporting, do you have
> the following comment in gcc/config/m68k/m68k.c ?
Yes, I checked that much. After that, I checked that
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46179
Summary: Codegen/TLS: invalid assembler syntax
Product: gcc
Version: 4.5.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassig...@