Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc/rft] [1/3] Remove stabs target macros: 	VARIABLES_INSIDE_BLOCK
Date: Fri, 05 Oct 2007 18:12:00 -0000	[thread overview]
Message-ID: <20071005181214.GA5316@caradoc.them.org> (raw)
In-Reply-To: <200710051805.l95I5D78029197@d12av02.megacenter.de.ibm.com>

On Fri, Oct 05, 2007 at 08:05:13PM +0200, Ulrich Weigand wrote:
> +/* Specify that for the native compiler variables for a particular
> +   lexical context are listed after the beginning LBRAC instead of
> +   before in the executables list of symbols.  */
> +static int
> +arm_variables_inside_block (int desc, int gcc_p)
> +{
> +  return !gcc_p;
> +}

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.

>  \f
>  static enum gdb_osabi
>  arm_elf_osabi_sniffer (bfd *abfd)
> @@ -3001,6 +3010,9 @@ arm_gdbarch_init (struct gdbarch_info in
>    set_gdbarch_coff_make_msymbol_special (gdbarch,
>  					 arm_coff_make_msymbol_special);
>  
> +  /* Specical STABS overrides.  */

Typo.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-10-05 18:12 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 [this message]
2007-10-08 11:34   ` Ulrich Weigand
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=20071005181214.GA5316@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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