From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC/commit] Getting rid of tm-rs6000.h (PROCESS_LINENUMBER_HOOK)
Date: Thu, 20 Sep 2007 06:10:00 -0000 [thread overview]
Message-ID: <200709200610.l8K6AeV1018876@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070918231448.GS29127@adacore.com> (message from Joel Brobecker on Tue, 18 Sep 2007 16:14:48 -0700)
> X-Spam-Check-By: sourceware.org
> Date: Tue, 18 Sep 2007 16:14:48 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Content-Disposition: inline
> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
> Sender: gdb-patches-owner@sourceware.org
> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information.
> X-UTwente-MailScanner: Found to be clean
> X-UTwente-MailScanner-From: gdb-patches-return-50837-m.m.kettenis=alumnus.utwente.nl@sourceware.org
> X-Spam-Status: No
> X-XS4ALL-DNSBL-Checked: mxdrop3.xs4all.nl checked 130.89.2.13 against DNS blacklists
> X-Virus-Scanned: by XS4ALL Virus Scanner
> X-XS4ALL-Spam-Score: 0.0 () DK_POLICY_SIGNSOME
> X-XS4ALL-Spam: NO
> X-CNFS-Analysis: v=1.0 c=1 a=5JwuhGrhyVAA:15 a=wfEPs4U+lFiAFA7pH+G9TA==:17 a=g1VYcl7afDL033UujJkA:9 a=oUFSmlPX7ia-zx2J8jsA:7 a=z6PKJkvbTO3t5axyC61YUgDJBJkA:4 a=b8hG5vVbyAkA:10 a=-y93oKWw6PMAJfIIPkkA:9 a=-0FndLuy2frk9IRV2UEA:7 a=zN-x5g51XQPJfcUlamfUbFjiEO0A:4 a=WZm9NgPvBkYA:10 a=5WZzfXpOq_gA:10 a=mDV3o1hIAAAA:8 a=vsAYgGIN1YtluYDjcCgA:9 a=al0t3wDx9O-uvKBlVngA:7 a=wYDCVDzEO6LVr6XnfH29QgUVgCgA:4 a=w2AolMDZV5cA:10 a=bClMUFNdNt6jSyT-7-0A:9 a=ZmXWUAE7x0GZgUYmYHgA:7 a=l2b_aCW9KmR25YviF7on3GO03rkA:4
> Envelope-To: mark.kettenis@xs4all.nl
> X-UIDL: 1190157346._smtp.mxdrop3.27993,S=16710
>
>
> --lrZ03NoBR/3+SXJZ
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> Hello,
>
> There is only one macro left in tm-rs6000.h, which is:
>
> /* In xcoff, we cannot process line numbers when we see them. This is
> mainly because we don't know the boundaries of the include files. So,
> we postpone that, and then enter and sort(?) the whole line table at
> once, when we are closing the current symbol table in end_symtab(). */
>
> #define PROCESS_LINENUMBER_HOOK() aix_process_linenos ()
> extern void aix_process_linenos (void);
>
> The AIX port is the only port that defines this macro, and it's only
> used in one place: buildsym.c:end_symtab(). I think the most appropriate
> way to define this notion is as a gdbarch method, set only in the case
> of AIX. This is what this patch does.
Hmm, if this is something that is purely for a specific object/debug format,
I think the gdbarch vector is the wrong place to put it.
Mark
next prev parent reply other threads:[~2007-09-20 6:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 23:15 Joel Brobecker
2007-09-20 6:10 ` Mark Kettenis [this message]
2007-09-20 6:37 ` Joel Brobecker
2007-09-20 9:04 ` Mark Kettenis
2007-09-20 21:13 ` Joel Brobecker
2007-09-21 7:48 ` Mark Kettenis
2007-09-21 18:03 ` Joel Brobecker
2007-10-02 17:38 ` Ulrich Weigand
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=200709200610.l8K6AeV1018876@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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