From: Jeffrey A Law <law@cygnus.com>
To: Joern Rennecke <amylaar@cygnus.co.uk>
Cc: mklein@dis.com (Mark Klein), gas2@cygnus.com, egcs@cygnus.com
Subject: Re: Questions regarding submittals
Date: Tue, 08 Sep 1998 02:22:00 -0000 [thread overview]
Message-ID: <2534.905246449@hurl.cygnus.com> (raw)
In-Reply-To: <199809072053.VAA01106@phal.cygnus.co.uk>
In message < 199809072053.VAA01106@phal.cygnus.co.uk >you write:
> > The hack that I used is to create a new pseudo directive in gas called
> > .compiler that takes a string argument in order to update the Compilation
> > Unit for each module. I modified ASM_IDENTIFY_GCC to include this pseudo
> > directive. However, that also means I needed to include the directive in
> > gcc/config/pa/*.asm. For MPE and the HP3000, that's OK because gas is the
> > only assembler available there. However, on HP-UX it is possible to not
> > use gas, and these directives would break that assembler.
> >
> > Is there a better way to approach this in order to communicate the pertin
> ent
> > information to gas in order to generate the SOM Compilation Unit records
> > in BFD for MPE without breaking things elsewhere?
>
> Where the existing ports need to emit this information, they use
> FILE_ASM_OP - usually defined to something like file or .file,
> or better, output_file_directive .
> output_file_directive uses ASM_OUTPUT_MAIN_SOURCE_FILENAME or
> ASM_OUTPUT_SOURCE_FILENAME, if defined.
>
> output_file_directive can be called from ASM_FILE_START; e.g. look at
> config/svr4.h .
.file already has a well defined syntax and meaning for gas and is
already in use on the PA port (note that PA port can not, does not,
and will not use svr4.h :-)
I believe Mark needs to pass more information than is available in a
.file directive.
I also believe it makes more sense from an assembler language standpoint
to have a clearer mapping from the assembler directive to what happens
in the object file. Thus I would prefer .compiler, .compilation_unit
or something like that over .file.
jeff
next prev parent reply other threads:[~1998-09-08 2:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-05 12:21 Mark Klein
1998-09-07 13:54 ` Joern Rennecke
1998-09-08 2:22 ` Jeffrey A Law [this message]
1998-09-08 13:05 ` Joern Rennecke
1998-09-08 14:02 ` Mark Klein
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=2534.905246449@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=gas2@cygnus.com \
--cc=mklein@dis.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).