Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	Elena Zannoni <ezannoni@redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] Multilibs and gdb.asm
Date: Fri, 05 Apr 2002 18:14:00 -0000	[thread overview]
Message-ID: <3CAE572C.95D08F17@redhat.com> (raw)
In-Reply-To: <3CAE1C31.6090001@cygnus.com>

Andrew Cagney wrote:
> 
> > On Fri, Apr 05, 2002 at 04:19:20PM -0500, Elena Zannoni wrote:
> >
> >>
> >> In gdb.asm/asm-source.exp, the testsuite passes multilib options to
> >> the assembler according to the compiler syntax.
> >> Obviously this doesn't work, as already noted by Nick Clifton in:
> >>
> >> http://sources.redhat.com/ml/gdb-patches/2002-01/msg00282.html
> >>
> >> A solution wasn't reached at the time.
> >>
> >> I found it useful to just bail out of the test if some multilibs were
> >> detected. At least it reduced the noise in the testsuite results.
> >>
> >> Is this too drastic?
> >
> >
> > I've got a silly suggestion.  Is there any reason not to assemble by
> > invoking the compiler, for this test?  Let it do all the multilib
> > footwork.
> 
> What compiler?  (There may be an assembler and linker but no compiler)

No, Daniel's right.  At some point last year, we changed the test
so that it invokes "gdb_compile" to do the final link.  I think that
was because the compiler would figure out what libraries needed to
be linked in.  I've been vaguely worried about that change...


  reply	other threads:[~2002-04-06  2:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 13:19 Elena Zannoni
2002-04-05 13:42 ` Daniel Jacobowitz
2002-04-05 13:50   ` Andrew Cagney
2002-04-05 18:14     ` Michael Snyder [this message]
2002-04-05 18:15   ` Michael Snyder
2002-04-05 14:30 ` Fernando Nasser
2002-04-05 15:05   ` Andrew Cagney
2002-04-07 17:10     ` Elena Zannoni

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=3CAE572C.95D08F17@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.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