public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Mark Klein <mklein@dis.com>
To: gas2@cygnus.com, egcs@cygnus.com
Subject: Questions regarding submittals
Date: Sat, 05 Sep 1998 12:21:00 -0000	[thread overview]
Message-ID: <3.0.3.32.19980905122057.00a5d100@garfield.dis.com> (raw)

I'm about to submit my changes to bfd, gas and egcs for my port of same
to the HP3000. However, before I do so, I have an ugly hack that I'd
like to discuss to see if maybe there is a better way to accomplish what
I need.

When doing an extract from a library on the HP3000, MPE requires that the
SOM Compilation Unit entries be filled in for each module, otherwise the
extract results in a object named UNNAMED.o. When extracting the various
tmplib*.a libraries to combine into libgcc.a, all the objects with the 
exception of the last object get lost as they keep overwriting UNNAMED.o.

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 pertinent
information to gas in order to generate the SOM Compilation Unit records 
in BFD for MPE without breaking things elsewhere?

Thanks in advance,


Mark
--
Mark Klein                                      DIS International, Ltd.
http://www.dis.com                              415-892-8400
PGP Public Key Available			Remove "nospam" to reply.

             reply	other threads:[~1998-09-05 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-05 12:21 Mark Klein [this message]
1998-09-07 13:54 ` Joern Rennecke
1998-09-08  2:22   ` Jeffrey A Law
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=3.0.3.32.19980905122057.00a5d100@garfield.dis.com \
    --to=mklein@dis.com \
    --cc=egcs@cygnus.com \
    --cc=gas2@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).