Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: Srikanth Adayapalam <srikanth@cup.hp.com>,
	gdb-patches@sourceware.cygnus.com
Subject: Re: (patch) hpjyg09: bcache optimizations
Date: Wed, 15 Dec 1999 01:16:00 -0000	[thread overview]
Message-ID: <970.945248225@upchuck> (raw)
In-Reply-To: <npyacciqf8.fsf@zwingli.cygnus.com>

  In message < npyacciqf8.fsf@zwingli.cygnus.com >you write:
  > 
  > > 	While it is true that it is not tied to the microprocessor,
  > > (and the placement of the macro is not ideal perhaps,) it is tied 
  > > somewhat to the HP-UX platform in that :
  > 
  > Ahh.  That, I didn't know.  So it would be correct to put the flag in
  > a file associated with a particular toolchain.
Not in this case.  While HP's tools arrange (via pxdb) to avoid duplicates,
other HP toolchains do not.

Short term none of the GNU toolchains on the PA remove duplicates.  That will
likely change for the PA64 toolchain (dwarf2 + elf), but it is unlikely to 
ever change for the PA32 toolchain (stabs + som).

In general, if we find ourselves tuning towards one particular toolchain, then
we are probably going down the wrong road.

jeff


  reply	other threads:[~1999-12-15  1:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-04 13:48 Jimmy Guo
1999-11-05  9:59 ` Jim Blandy
1999-11-05 10:50   ` Srikanth Adayapalam
1999-11-05 13:29     ` Jim Blandy
1999-12-15  1:16       ` Jeffrey A Law [this message]
1999-12-16  0:26   ` Jeffrey A Law
     [not found] <Pine.LNX.4.10.9911041529510.15357-100000@hpcll168.cup.hp.com>
1999-11-04 17:31 ` Andrew Cagney

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=970.945248225@upchuck \
    --to=law@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=jimb@cygnus.com \
    --cc=srikanth@cup.hp.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