Excise C++ style comments.

This commit is contained in:
Alan Modra
2000-10-04 00:28:45 +00:00
parent 69dc947abb
commit 56d27c17b8
3 changed files with 25 additions and 18 deletions

View File

@ -1,3 +1,8 @@
2000-10-04 Ralf Baechle <ralf@gnu.org>
* config/tc-ia64.c (operand_match): Don't use // style comments.
* config/tc-i370.c: Likewise.
2000-09-29 Hans-Peter Nilsson <hp@axis.com>
Changes to handle varying register prefix and user symbol prefix.
@ -83,7 +88,7 @@
2000-09-22 Michael Sokolov <msokolov@ivan.Harhan.ORG>
* config/tc-m68k.c (md_relax_table, m68k_ip, md_convert_frag_1,
* config/tc-m68k.c (md_relax_table, m68k_ip, md_convert_frag_1,
md_estimate_size_before_relax): Redesign and clean up the
relaxation mechanism.
@ -161,7 +166,7 @@
(struct rsrc): Add parallel comparison type.
(resources_match): Skip special cases of PR usage (non-conflicting
parallel compares).
2000-09-13 Kazu Hirata <kazu@hxi.com>
* config/obj-ecoff.c: Fix formatting.
@ -176,7 +181,7 @@
* config/obj-vms.h: Likewise.
2000-09-13 Anders Norlander <anorland@acc.umu.se>
* config/tc-mips.c (md_begin): Recognize 4Kc, 4Km and 4Kp processors.
(md_parse_option): Ditto.
(md_longopts): Add -mips32 option.

View File

@ -552,7 +552,7 @@ i370_set_cpu ()
}
/* Figure out the BFD architecture to use. */
// hack alert -- specify the different 370 architectures
/* hack alert -- specify the different 370 architectures */
enum bfd_architecture
i370_arch ()
@ -656,14 +656,13 @@ i370_insert_operand (insn, operand, val)
#ifdef OBJ_ELF
/* Parse @got, etc. and return the desired relocation.
* Currently, i370 does not support (don't really need to support) any
* of these fancier markups ... for example, no one is going to
* write 'L 6,=V(bogus)@got' it just doesn't make sense (at least to me).
* So basically, we could get away with this routine returning
* BFD_RELOC_UNUSED in all circumstances. However, I'll leave
* in for now in case someone ambitious finds a good use for this stuff ...
* this routine was pretty much just copied from the powerpc code ...
*/
Currently, i370 does not support (don't really need to support) any
of these fancier markups ... for example, no one is going to
write 'L 6,=V(bogus)@got' it just doesn't make sense (at least to me).
So basically, we could get away with this routine returning
BFD_RELOC_UNUSED in all circumstances. However, I'll leave
in for now in case someone ambitious finds a good use for this stuff ...
this routine was pretty much just copied from the powerpc code ... */
static bfd_reloc_code_real_type
i370_elf_suffix (str_p, exp_p)
char **str_p;
@ -687,11 +686,14 @@ i370_elf_suffix (str_p, exp_p)
static struct map_bfd mapping[] =
{
// MAP ("l", BFD_RELOC_LO16),
// MAP ("h", BFD_RELOC_HI16),
// MAP ("ha", BFD_RELOC_HI16_S),
MAP ("fixup", BFD_RELOC_CTOR), /* warnings with -mrelocatable */
{ (char *)0, 0, BFD_RELOC_UNUSED }
#if 0
MAP ("l", BFD_RELOC_LO16),
MAP ("h", BFD_RELOC_HI16),
MAP ("ha", BFD_RELOC_HI16_S),
#endif
/* warnings with -mrelocatable. */
MAP ("fixup", BFD_RELOC_CTOR),
{ (char *)0, 0, BFD_RELOC_UNUSED }
};
if (*str++ != '@')

View File

@ -7910,7 +7910,7 @@ note_register_values (idesc)
else if (strncmp (idesc->name, "br.call", 6) == 0
|| strncmp (idesc->name, "brl.call", 7) == 0)
{
// FIXME keep GR values which are marked as "safe_across_calls"
/* FIXME keep GR values which are marked as "safe_across_calls" */
clear_register_values ();
clear_qp_mutex (~qp_safe_across_calls);
clear_qp_implies (~qp_safe_across_calls, ~qp_safe_across_calls);