From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Roman Zippel <zippel@linux-m68k.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH][2/3] Unbreak m68k bootstrap
Date: Sun, 14 Oct 2007 10:11:00 -0000 [thread overview]
Message-ID: <4711EA11.8060603@codesourcery.com> (raw)
In-Reply-To: <4711E7FF.7010002@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
Hello Andreas,
This patch fixes one of bootstrap failure issues on m68k.
The patch in neighboring thread (1/3) enables use of autogenerated enums
for instruction attributes in <arch>-protos.h header. This patch
applies that to fix bootstrap-time warning.
The patch was bootstrapped on m68k-unknown-linux-gnu with
enable-languages=c.
OK for trunk?
:ADDPATCH m68k:
Thanks,
Maxim
[-- Attachment #2: m68k-v2.ChangeLog --]
[-- Type: text/plain, Size: 282 bytes --]
2007-10-12 Maxim Kuvyrkov <maxim@codesourcery.com>
* config/m68k/m68k.h (m68k_sched_cpu, m68k_sched_attr_opx_type,
m68k_sched_attr_opy_type, m68k_sched_attr_size, m68k_sched_attr_op_mem,
m68k_sched_branch_type): Move declarations to ...
* config/m68/m68k-protos.h: ... here.
[-- Attachment #3: m68k-v2.patch --]
[-- Type: text/plain, Size: 1450 bytes --]
Index: config/m68k/m68k.h
===================================================================
--- config/m68k/m68k.h (revision 184625)
+++ config/m68k/m68k.h (working copy)
@@ -1148,10 +1148,3 @@ extern M68K_CONST_METHOD m68k_const_meth
extern void m68k_emit_move_double (rtx [2]);
-extern enum attr_cpu m68k_sched_cpu;
-
-extern enum attr_opx_type m68k_sched_attr_opx_type (rtx, int);
-extern enum attr_opy_type m68k_sched_attr_opy_type (rtx, int);
-extern int m68k_sched_attr_size (rtx);
-extern enum attr_op_mem m68k_sched_attr_op_mem (rtx);
-extern enum attr_type m68k_sched_branch_type (rtx);
Index: config/m68k/m68k-protos.h
===================================================================
--- config/m68k/m68k-protos.h (revision 184625)
+++ config/m68k/m68k-protos.h (working copy)
@@ -65,6 +65,16 @@ extern int emit_move_sequence (rtx *, en
extern bool m68k_movem_pattern_p (rtx, rtx, HOST_WIDE_INT, bool);
extern const char *m68k_output_movem (rtx *, rtx, HOST_WIDE_INT, bool);
+#ifdef HAVE_ATTR_cpu
+extern enum attr_cpu m68k_sched_cpu;
+
+extern enum attr_opx_type m68k_sched_attr_opx_type (rtx, int);
+extern enum attr_opy_type m68k_sched_attr_opy_type (rtx, int);
+extern int m68k_sched_attr_size (rtx);
+extern enum attr_op_mem m68k_sched_attr_op_mem (rtx);
+extern enum attr_type m68k_sched_branch_type (rtx);
+#endif /* HAVE_ATTR_cpu */
+
#endif /* RTX_CODE */
extern bool m68k_regno_mode_ok (int, enum machine_mode);
next prev parent reply other threads:[~2007-10-14 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 10:06 Maxim Kuvyrkov
2007-10-14 10:08 ` [PATCH][1/3] " Maxim Kuvyrkov
2007-10-17 17:46 ` Ian Lance Taylor
2007-10-14 10:11 ` Maxim Kuvyrkov [this message]
2007-10-16 14:25 ` [PATCH][2/3] " Andreas Schwab
2007-10-14 10:16 ` [PATCH][3/3] " Maxim Kuvyrkov
2007-10-17 17:21 ` Ian Lance Taylor
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=4711EA11.8060603@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@suse.de \
--cc=zippel@linux-m68k.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).