public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/8516] Build of gdb-6.0 on hppa1.1-hp-hpux10.20 fails
Date: Fri, 30 Jul 2010 10:19:00 -0000	[thread overview]
Message-ID: <20100730101944.23810.qmail@sourceware.org> (raw)
In-Reply-To: <20031007181800.8516.dave.anglin@nrc-cnrc.gc.ca>


------- Additional Comments From pedro at codesourcery dot com  2010-07-30 10:19 -------
Thanks Dave.

Hmmm, hpux-thread.c is:

 - implemented on top of deprecated_child_ops.  deprecated_child_ops is
   just a dummy target that does nothing.  This was an alternative to removing
   hpux-thread.c completely at some point in the past.  So this file is just
   dead wait at this point, patiently waiting for someone to salvage it.

 - implemented as a process_stratum target using the ancient
   child_suppress_run hack.  Salvaging this target would mean turning it
   into a thread_stratum target.  I'm looking at the code, and I can
   tell you that without adding any new features, just translating the
   mechanisms, that most of the file would disappear.  The mildly interesting
   bits left are the register access code, and the objfile callback that
   detects the thread support is active in the inferior.  We're talking about
   a couple dozens of lines of code.

 - The bit rot breaking the build is now in the register access code...

So, although the build breakage this time is probably easy to fix, IMO,
we should just move the file into the attic.  It may
be even less work to start from scratch than to resurrect it into functional
state.  The file will always be in the attic for anyone wanting to salvage
this.  (I didn't go look for the current debian patch to see what they did to
this file.)

Comments/Objections?


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|SUSPENDED                   |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=8516

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2010-07-30 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031007181800.8516.dave.anglin@nrc-cnrc.gc.ca>
2010-07-29 19:40 ` danglin at gcc dot gnu dot org
2010-07-30 10:19 ` pedro at codesourcery dot com [this message]
     [not found] <bug-8516-4717@http.sourceware.org/bugzilla/>
2012-10-24 16:55 ` palves at redhat dot com
2012-10-27 14:08 ` danglin at gcc dot gnu.org

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=20100730101944.23810.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).