From: Ian Lance Taylor <ian@cygnus.com>
To: Aymeric.Vincent@emi.u-bordeaux.fr
Cc: bfd@cygnus.com
Subject: Re: adding a new target (m68k-gnu)
Date: Sun, 06 Dec 1998 13:53:00 -0000 [thread overview]
Message-ID: <199812062153.QAA05293@subrogation.cygnus.com> (raw)
In-Reply-To: <199810271207.NAA15953@aliboron.emi.u-bordeaux.fr>
Date: Tue, 27 Oct 1998 15:12:03 +0100
From: Aymeric Vincent <Aymeric.Vincent@emi.u-bordeaux.fr>
Could you please add a new m68k-gnu target to the binutils? It's
basically an elf target, like i386-gnu (without mach3 stuff) or
m68k-linux.
I patched bfd/config.bfd, gas/configure.in, and ld/configure.tgt for
m68k-gnu. Sorry about the long delay.
I would like to have REGISTER_PREFIX_OPTIONAL set for this target, but
didn't figure out where it had to be put... I just put it in tc-m68k.h
(as described below), but it's of course a stupid solution, which did
the trick for what I had to do...
I don't understand why you want to make this change. This is normally
the wrong thing to do for an m68k ELF target. The macro only exists
for target with a lot of legacy m68k code which does not use register
prefixes, but presumably that is not the case for m68k-gnu. The flag
should not normally be set when compiling C code, unless the compiler
has been modified to use leading underscores on symbol names;
otherwise, the flag can cause gas to misassemble C code which uses
function or global variables with names that happen to be the same as
m68k register names.
Ian
next prev parent reply other threads:[~1998-12-06 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-27 4:07 Aymeric Vincent
1998-12-06 13:53 ` Ian Lance Taylor [this message]
1998-12-07 3:23 ` Aymeric Vincent
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=199812062153.QAA05293@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=Aymeric.Vincent@emi.u-bordeaux.fr \
--cc=bfd@cygnus.com \
/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).