1999-05-03 09:29:11 +02:00
|
|
|
/* BFD support for the ARC processor
|
2019-01-01 11:31:27 +01:00
|
|
|
Copyright (C) 1994-2019 Free Software Foundation, Inc.
|
1999-05-03 09:29:11 +02:00
|
|
|
Contributed by Doug Evans (dje@cygnus.com).
|
|
|
|
|
2007-07-03 16:26:43 +02:00
|
|
|
This file is part of BFD, the Binary File Descriptor library.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2007-07-03 16:26:43 +02:00
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
|
|
it under the terms of the GNU General Public License as published by
|
|
|
|
the Free Software Foundation; either version 3 of the License, or
|
|
|
|
(at your option) any later version.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2007-07-03 16:26:43 +02:00
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
GNU General Public License for more details.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2007-07-03 16:26:43 +02:00
|
|
|
You should have received a copy of the GNU General Public License
|
|
|
|
along with this program; if not, write to the Free Software
|
|
|
|
Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston,
|
|
|
|
MA 02110-1301, USA. */
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
#include "sysdep.h"
|
2007-04-26 16:47:00 +02:00
|
|
|
#include "bfd.h"
|
1999-05-03 09:29:11 +02:00
|
|
|
#include "libbfd.h"
|
|
|
|
|
[ARC] Implement compatible function for ARC BFD architectures
The general rule for bfd_arch_info_type->compatible (A, B) is that if A and B
are compatible, then this function should return architecture that is more
"feature-rich", that is, can run both A and B. ARCv2, EM and HS all has same
mach number, so bfd_default_compatible assumes they are the same, and returns
an A. That causes issues with GDB, because GDB assumes that if machines are
compatible, then "compatible ()" always returns same machine regardless of
argument order. As a result GDB gets confused because, for example,
compatible(ARCv2, EM) returns ARCv2, but compatible(EM, ARCv2) returns EM,
hence GDB is not sure if they are compatible and prints a warning.
bfd/ChangeLog:
yyyy-mm-dd Anton Kolesov Anton.Kolesov@synopsys.com
cpu-arc.c (arc_compatible): New function.
2017-03-17 16:37:42 +01:00
|
|
|
static const bfd_arch_info_type *
|
|
|
|
arc_compatible (const bfd_arch_info_type *a, const bfd_arch_info_type *b);
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
#define ARC(mach, print_name, default_p, next) \
|
2019-09-10 16:20:58 +02:00
|
|
|
{ \
|
|
|
|
32, /* Bits in a word. */ \
|
|
|
|
32, /* Bits in an address. */ \
|
|
|
|
8, /* Bits in a byte. */ \
|
1999-05-03 09:29:11 +02:00
|
|
|
bfd_arch_arc, \
|
|
|
|
mach, \
|
|
|
|
"arc", \
|
|
|
|
print_name, \
|
2019-09-10 16:20:58 +02:00
|
|
|
4, /* Section alignment power. */ \
|
1999-05-03 09:29:11 +02:00
|
|
|
default_p, \
|
[ARC] Implement compatible function for ARC BFD architectures
The general rule for bfd_arch_info_type->compatible (A, B) is that if A and B
are compatible, then this function should return architecture that is more
"feature-rich", that is, can run both A and B. ARCv2, EM and HS all has same
mach number, so bfd_default_compatible assumes they are the same, and returns
an A. That causes issues with GDB, because GDB assumes that if machines are
compatible, then "compatible ()" always returns same machine regardless of
argument order. As a result GDB gets confused because, for example,
compatible(ARCv2, EM) returns ARCv2, but compatible(EM, ARCv2) returns EM,
hence GDB is not sure if they are compatible and prints a warning.
bfd/ChangeLog:
yyyy-mm-dd Anton Kolesov Anton.Kolesov@synopsys.com
cpu-arc.c (arc_compatible): New function.
2017-03-17 16:37:42 +01:00
|
|
|
arc_compatible, \
|
1999-05-03 09:29:11 +02:00
|
|
|
bfd_default_scan, \
|
2012-01-31 18:54:39 +01:00
|
|
|
bfd_arch_default_fill, \
|
1999-05-03 09:29:11 +02:00
|
|
|
next, \
|
2019-09-10 16:20:58 +02:00
|
|
|
0 /* Maximum offset of a reloc from the start of an insn. */ \
|
1999-05-03 09:29:11 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
static const bfd_arch_info_type arch_info_struct[] =
|
|
|
|
{
|
2017-03-17 14:43:31 +01:00
|
|
|
ARC (bfd_mach_arc_arc600, "A6" , FALSE, &arch_info_struct[1]),
|
|
|
|
ARC (bfd_mach_arc_arc601, "ARC601", FALSE, &arch_info_struct[2]),
|
|
|
|
ARC (bfd_mach_arc_arc700, "ARC700", FALSE, &arch_info_struct[3]),
|
|
|
|
ARC (bfd_mach_arc_arc700, "A7", FALSE, &arch_info_struct[4]),
|
|
|
|
ARC (bfd_mach_arc_arcv2, "ARCv2", FALSE, &arch_info_struct[5]),
|
|
|
|
ARC (bfd_mach_arc_arcv2, "EM", FALSE, &arch_info_struct[6]),
|
2015-10-07 15:20:19 +02:00
|
|
|
ARC (bfd_mach_arc_arcv2, "HS", FALSE, NULL),
|
1999-05-03 09:29:11 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
const bfd_arch_info_type bfd_arc_arch =
|
2016-02-05 10:58:01 +01:00
|
|
|
ARC (bfd_mach_arc_arc600, "ARC600", TRUE, &arch_info_struct[0]);
|
[ARC] Implement compatible function for ARC BFD architectures
The general rule for bfd_arch_info_type->compatible (A, B) is that if A and B
are compatible, then this function should return architecture that is more
"feature-rich", that is, can run both A and B. ARCv2, EM and HS all has same
mach number, so bfd_default_compatible assumes they are the same, and returns
an A. That causes issues with GDB, because GDB assumes that if machines are
compatible, then "compatible ()" always returns same machine regardless of
argument order. As a result GDB gets confused because, for example,
compatible(ARCv2, EM) returns ARCv2, but compatible(EM, ARCv2) returns EM,
hence GDB is not sure if they are compatible and prints a warning.
bfd/ChangeLog:
yyyy-mm-dd Anton Kolesov Anton.Kolesov@synopsys.com
cpu-arc.c (arc_compatible): New function.
2017-03-17 16:37:42 +01:00
|
|
|
|
|
|
|
/* ARC-specific "compatible" function. The general rule is that if A and B are
|
|
|
|
compatible, then this function should return architecture that is more
|
|
|
|
"feature-rich", that is, can run both A and B. ARCv2, EM and HS all has
|
|
|
|
same mach number, so bfd_default_compatible assumes they are the same, and
|
|
|
|
returns an A. That causes issues with GDB, because GDB assumes that if
|
|
|
|
machines are compatible, then "compatible ()" always returns same machine
|
|
|
|
regardless of argument order. As a result GDB gets confused because, for
|
|
|
|
example, compatible (ARCv2, EM) returns ARCv2, but compatible (EM, ARCv2)
|
|
|
|
returns EM, hence GDB is not sure if they are compatible and prints a
|
|
|
|
warning. */
|
|
|
|
|
|
|
|
static const bfd_arch_info_type *
|
|
|
|
arc_compatible (const bfd_arch_info_type *a, const bfd_arch_info_type *b)
|
|
|
|
{
|
|
|
|
const bfd_arch_info_type * const em = &arch_info_struct[5];
|
|
|
|
const bfd_arch_info_type * const hs = &arch_info_struct[6];
|
|
|
|
|
|
|
|
/* Trivial case where a and b is the same instance. Some callers already
|
|
|
|
check this condition but some do not and get an invalid result. */
|
|
|
|
if (a == b)
|
|
|
|
return a;
|
|
|
|
|
|
|
|
/* If a & b are for different architecture we can do nothing. */
|
|
|
|
if (a->arch != b->arch)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
if (a->bits_per_word != b->bits_per_word)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
/* ARCv2|EM and EM. */
|
|
|
|
if ((a->mach == bfd_mach_arc_arcv2 && b == em)
|
|
|
|
|| (b->mach == bfd_mach_arc_arcv2 && a == em))
|
|
|
|
return em;
|
|
|
|
|
|
|
|
/* ARCv2|HS and HS. */
|
|
|
|
if ((a->mach == bfd_mach_arc_arcv2 && b == hs)
|
|
|
|
|| (b->mach == bfd_mach_arc_arcv2 && a == hs))
|
|
|
|
return hs;
|
|
|
|
|
|
|
|
return bfd_default_compatible (a, b);
|
|
|
|
}
|