This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
gas: flag_mri vs. flag_m68k_mri vs. macro_mri
- From: "Jan Beulich" <JBeulich at novell dot com>
- To: <binutils at sources dot redhat dot com>
- Date: Tue, 25 Jan 2005 12:47:23 +0100
- Subject: gas: flag_mri vs. flag_m68k_mri vs. macro_mri
Can anyone tell me what the reason for duplicating the information held
by these three variables is? macro_mri exactly follows flag_mri, and
flag_m68k_mri, for the only case where it is not #define-d to 0, also
does. Thus it would seem to me that macro_mri could be replaced by
flag_mri; for flag_m68k_mri it would need to be checked whether there
indeed are differences between MRI mode under TC_M68K vs. all other
architectures. If so, (at least) some of the macro handling (e.g.
buffer_and_nest) seems to incorrectly refer to macro_mri where I would
think flag_m68k_mri is meant.
Thanks, Jan