From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc/rft] [1/3] Remove stabs target macros: VARIABLES_INSIDE_BLOCK
Date: Mon, 08 Oct 2007 11:34:00 -0000 [thread overview]
Message-ID: <200710081134.l98BY4t2029484@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20071005181214.GA5316@caradoc.them.org> from "Daniel Jacobowitz" at Oct 05, 2007 02:12:14 PM
Daniel Jacobowitz wrote:
> Does anyone reading this know what native compiler is meant here?
> I suspect it is an ancient comment, probably back as far as RiscOS.
> In that case there's no reason to keep the variable.
It looks like the variable was introduced with the initial version
of the m-arm.h file in 1990, so this is certainly ancient.
Tue Feb 13 00:08:27 1990 Jim Kingdon (kingdon at pogo.ai.mit.edu)
* m-arm.h, arm-dep.c arm-pinsn.c arm-opcode.h: New files.
dbxread.c, m-convex.h (VARIABLES_INSIDE_BLOCK): Add gcc_p parameter.
Makefile.dist (alldeps.mak): Special case for arm-convert.s.
dbxread.c (define_symbol): Check for local based on it not
being any one of the known deftypes.
values.c (using_struct_return): Use new macro USE_STRUCT_CONVENTION.
Just removing it would certainly be fine with me; should we do that?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-10-08 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 18:05 Ulrich Weigand
2007-10-05 18:12 ` Daniel Jacobowitz
2007-10-08 11:34 ` Ulrich Weigand [this message]
2007-10-11 19:08 ` Daniel Jacobowitz
2007-10-11 19:48 ` Ulrich Weigand
2007-10-06 7:07 ` Eli Zaretskii
2007-10-06 7:44 ` Eli Zaretskii
2007-10-08 11:09 ` 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=200710081134.l98BY4t2029484@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--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