Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jie Zhang <jzhang918@gmail.com>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add support for Analog Devices Blackfin processor (part 3/6: gdb testsuite)
Date: Wed, 04 Jan 2006 06:41:00 -0000	[thread overview]
Message-ID: <6f48278f0601032241j18428d3ay6c3c9df5cb878e8b@mail.gmail.com> (raw)
In-Reply-To: <8f2776cb0601032131v584c465djaca0483556409c86@mail.gmail.com>

Hi Jim,

Thanks a lot for reviewing these patches!

On 1/4/06, Jim Blandy <jimb@red-bean.com> wrote:
> On 12/27/05, Jie Zhang <jzhang918@gmail.com> wrote:
> +        set asm-flags "-I${srcdir}/${subdir} -I${objdir}/${subdir}"
>
> What's the story behind these -I flags that seem to be sprouting up in
> a lot of the cases in asm-source.exp?  It seems like they should
> either be necessary everywhere, or nowhere.
>
This is the easiest question for me, so I answer it first.

In asm-source.exp, first comes:

set asm-flags ""

After all target things, there is:

if { "${asm-flags}" == "" } {
    set asm-flags "-I${srcdir}/${subdir} -I${objdir}/${subdir}"
    set debug-flags "-gstabs"
}

So if target does not set asm-flags, the debug-flags will be set to
"-gstabs", which will override anything target set for it. If any
target want to use dwarf2 as debug information, like bfin and others,
it needs set asm-flags to the vanilla string to avoid the overriding.

Regards,
Jie


  reply	other threads:[~2006-01-04  6:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-30 10:13 Jie Zhang
2006-01-04  5:32 ` Jim Blandy
2006-01-04  6:41   ` Jie Zhang [this message]
2006-01-04  8:22     ` Jim Blandy
2006-01-20 23:22       ` Daniel Jacobowitz

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=6f48278f0601032241j18428d3ay6c3c9df5cb878e8b@mail.gmail.com \
    --to=jzhang918@gmail.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@red-bean.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