X-Git-Url: http://git.sourceforge.jp/view?p=pf3gnuchains%2Fgcc-fork.git;a=blobdiff_plain;f=gcc%2Fconfig%2Fm68k%2Fm68k.c;fp=gcc%2Fconfig%2Fm68k%2Fm68k.c;h=3e463023625e21eb54f4dbae5a0ebc6f5f177278;hp=ce028a02a6608ef0fb638d434a86e4a158a7fa81;hb=bc409cb4a41d267365a3f085add7808cdc8e134f;hpb=c8dd516d9e1a44225ebfde67a38146301709f9ab

diff --git a/gcc/config/m68k/m68k.c b/gcc/config/m68k/m68k.c
index ce028a02a66..3e463023625 100644
--- a/gcc/config/m68k/m68k.c
+++ b/gcc/config/m68k/m68k.c
@@ -4269,7 +4269,7 @@ strict_low_part_peephole_ok (enum machine_mode mode, rtx first_insn,
    simple fact that the m68k does not allow a pc-relative addressing
    mode as a destination.  gcc does not distinguish between source and
    destination addresses.  Hence, if we claim that pc-relative address
-   modes are valid, e.g. GO_IF_LEGITIMATE_ADDRESS accepts them, then we
+   modes are valid, e.g. TARGET_LEGITIMATE_ADDRESS_P accepts them, then we
    end up with invalid code.  To get around this problem, we left
    pc-relative modes as invalid addresses, and then added special
    predicates and constraints to accept them.