public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Serge Nikulin" <nikulin@actsw.amat.com>
To: <cal_erickson@mvista.com>, <insight@sourceware.cygnus.com>
Subject: Re: How to embed path info into assembler sources?
Date: Thu, 13 Jul 2000 14:38:00 -0000	[thread overview]
Message-ID: <001301bfed12$62bcd540$35758798@mis.amat.com> (raw)
In-Reply-To: <396E156C.A427B893@mvista.com>

Cal,

> This is an interesting problem. By default the m68k assembler produces
iee695
> files as output. These files would have the path information in them for
debug.
> If you are running a very old m68k assembler that produces coff output

I do not use MRI's assembler.
my assembler is a standard GNU binutils-2.9.1 as assembler (aka GAS).
It was targeted as --target=m68k-coff
The resulting executable is m68k-coff-as.exe
My sources ARE MRI-compatible.
As a matter of fact, I have to maintain this MRI compatibility because other
folks over here
still use MRI tools to build the project.

So the problem is with GAS.
GAS does not  incorporate path info into objects.
In comparison, gcc incorporates path info into intermediate *.s sources.
But it does it in native GAS format (.stabs). Apparently GAS in MRI mode
does not understand these stabs.

The question is how to incorporate pathinfo into the object file or into the
final abs file.




  parent reply	other threads:[~2000-07-13 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-13 10:29 Serge Nikulin
2000-07-13 10:57 ` Cal Erickson
2000-07-13 11:19   ` Serge Nikulin
     [not found]     ` <396E156C.A427B893@mvista.com>
2000-07-13 14:38       ` Serge Nikulin [this message]
2000-07-14  6:01         ` Keith Seitz

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='001301bfed12$62bcd540$35758798@mis.amat.com' \
    --to=nikulin@actsw.amat.com \
    --cc=cal_erickson@mvista.com \
    --cc=insight@sourceware.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).