Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: kettenis@chello.nl
Cc: nickc@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: RFA/RFC: Change Sparc64 gdb.asm tests to use -gdwarf2 instead of  -gstabs
Date: Thu, 29 Jul 2004 23:38:00 -0000	[thread overview]
Message-ID: <41098A7B.nail5AP1O5DT4@mindspring.com> (raw)
In-Reply-To: <200407292303.i6TN30SB024149@elgar.kettenis.dyndns.org>

Mark Kettenis <kettenis@chello.nl> wrote:
> Not all right!  Nick, did you actually test this patch?

Yes, he did.

If you keep reading the thread, you can see that I asked Nick to
test with "dwarf-2" and "stabs+", and Nick actually tested with
"dwarf2" and "stabs+" (which source.exp translates to "stabs").
But it looks like Nick's tests did not actually test.  :(

> The subject of this thread is making sparc64 use -gdwarf2 instead of
> -gstabs, but > the patch changes it to -gdwarf-2 (note the extra
> dash).  This isn't accepted by gas on my OpenBSD/amd64 and
> OpenBSD/sparc64 systems, and AFAICT it isn't accepted by the current
> gas from CVS either.

Hmmm.  Ick.  You're right.  Nick tested with "dwarf2" on the command
line, but the patch says "dwarf-2" embedded in the code.  And
the assembler spells "dwarf2" differently from gcc, which spells
it "dwarf-2".  And to make matters more confusing, old assemblers
do not understand "stabs+", but as 2.15 does support stabs+ with
new extensions.

For dwarf-2, I'd like to spell it the same way everywhere, and
translate it at the last moment for binutils.  That way, people
can run the test suite with:

  make check RUNTESTFLAGS="--target_board unix/gdb:debug_flags=dwarf-2"

... and will get dwarf-2 with all languages.

Like this:

  # The GNU assembler spells dwarf-2 as "dwarf2".
  if { ${debug-flags} == "-gdwarf-2" } then {
    set debug-flags "-gdwarf2"
  }

Mark, does that work on your system?

I'll test it on my system later tonight.

Michael C


  reply	other threads:[~2004-07-29 23:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 12:59 Nick Clifton
     [not found] ` <41051014 dot nailLY111456S at mindspring dot com>
2004-07-26 14:07 ` Michael Chastain
2004-07-26 17:31   ` Nick Clifton
2004-07-26 23:55     ` Michael Chastain
2004-07-29 23:03       ` Mark Kettenis
2004-07-29 23:38         ` Michael Chastain [this message]
2004-07-30  0:07           ` Mark Kettenis
2004-07-30 11:55         ` Nick Clifton

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=41098A7B.nail5AP1O5DT4@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    --cc=nickc@redhat.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