From: Gunther Nikl <gni@gecko.de>
To: Bernardo Innocenti <bernie@develer.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Testing m68k changes on AmigaOS and Linux/m68k
Date: Mon, 13 Oct 2003 17:24:00 -0000 [thread overview]
Message-ID: <20031013152223.GA45308@lorien.int.gecko.de> (raw)
In-Reply-To: <3F88BBCF.7090106@develer.com>
Hello Bernardo,
> I've recently applied all my remaining m68k patches.
Your changes caused some breakage for my patches ;-)
> Since I can only test on ColdFire targets, would you mind doing a
> bootstrap on Linux/m68k and/or AmigaOS?
I maintain my patches on a cross-setup by building a cross-compiler.
That cross-compiler is then used to build a "native" compiler for my
target. I don't boostrap on the target because thats much to slow for
my taste ;-(
Building the cross-compiler revealed two errors in m68k.c. The patch is
attached. Using the cross-compiler to built the native compiler revealed
two bugs (?) in gcc/Makefile[.in]. I changed the Makefile and was able
to build the native compiler but I don't know whether my changes to the
Makefile are correct. The cross-compiler to AmigaOS seems to work
correctly (modulo the open issues regarding small-data). I goint to test
the coss-built native compiler tonight.
Gunther
--cut--
2003-10-13 Gunther Nikl <gni@gecko.de>
* config/m68k/m68k.c (m68k_output_function_prologue): Fix usage of
current_frame at two places (one type and one missing)
--- m68k.c.orig Mon Oct 13 11:35:20 2003
+++ m68k.c Mon Oct 13 14:48:23 2003
@@ -623,7 +623,7 @@
#ifdef MOTOROLA
asm_fprintf (stream, "\tfmovm %I0x%x,-(%Rsp)\n", current_frame.fpu_mask);
#else
- asm_fprintf (stream, "\tfmovem %I0x%x,%Rsp@-\n", current_frmae.fpu_mask);
+ asm_fprintf (stream, "\tfmovem %I0x%x,%Rsp@-\n", current_frame.fpu_mask);
#endif
if (dwarf2out_do_frame ())
{
@@ -934,7 +934,7 @@
#else
asm_fprintf (stream, "\tmoveml %s@(-%wd),%I0x%x\n",
reg_names[FRAME_POINTER_REGNUM],
- offset + fsize,
+ current_frame.offset + fsize,
current_frame.reg_mask);
#endif
}
--cut--
next prev parent reply other threads:[~2003-10-13 15:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 4:07 Bernardo Innocenti
2003-10-13 17:24 ` Gunther Nikl [this message]
2003-10-14 12:40 ` Bernardo Innocenti
2003-10-14 13:56 ` Gunther Nikl
2003-10-14 17:00 ` Bernardo Innocenti
2003-10-15 12:40 ` Gunther Nikl
2003-10-15 17:42 ` Gunther Nikl
2003-10-15 20:53 ` Bernardo Innocenti
2003-10-15 21:18 ` Andreas Schwab
2003-10-16 15:27 ` Gunther Nikl
2003-10-16 16:36 ` Andreas Schwab
2003-10-16 17:27 ` Bernardo Innocenti
2003-10-21 14:38 ` Gunther Nikl
2003-10-21 20:33 ` Bernardo Innocenti
2003-10-23 16:11 ` Gunther Nikl
2003-10-23 20:30 ` Bernardo Innocenti
2003-10-24 13:49 ` Gunther Nikl
2003-10-25 6:04 ` Bernardo Innocenti
2003-10-15 13:57 ` Gunther Nikl
2003-10-31 23:47 ` Matthias Klose
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=20031013152223.GA45308@lorien.int.gecko.de \
--to=gni@gecko.de \
--cc=bernie@develer.com \
--cc=gcc@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).