Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Andrew Pinski <andrew.pinski@caviumnetworks.com>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>,
	       "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH/MIPS] Add support Octeon's bbit instructions
Date: Thu, 23 Aug 2012 16:27:00 -0000	[thread overview]
Message-ID: <87d32hpo9m.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CA+=Sn1kktQHNzbyLAEKDk+=Dau_V8nEkmW9_pUPMtWyNAjwpxg@mail.gmail.com>	(Andrew Pinski's message of "Sun, 19 Aug 2012 15:19:19 -0700")

>>>>> "Andrew" == Andrew Pinski <andrew.pinski@caviumnetworks.com> writes:

I know this is in already, but at least for future reference (or now if
you don't mind changing it)...

Andrew> +set testfile "mips-octeon-bbit"
Andrew> +set srcfile ${testfile}.c
Andrew> +set binfile ${objdir}/${subdir}/${testfile}

Use standard_testfile.c

Andrew> +if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable \
Andrew> +       {debug nowarnings}] != "" } {
Andrew> +     fail "compilation"
Andrew> +     return
Andrew> +}
Andrew> +
Andrew> +pass "compilation"
Andrew> +
Andrew> +gdb_exit
Andrew> +gdb_start
Andrew> +gdb_reinitialize_dir $srcdir/$subdir
Andrew> +gdb_load ${binfile}

All this can be replaced with prepare_for_testing.

If you want, I can write a patch, if you would test it.

thanks,
Tom


  reply	other threads:[~2012-08-23 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 16:49 Andrew Pinski
2012-04-19 13:38 ` Maciej W. Rozycki
2012-04-20 22:56   ` Pinski, Andrew
2012-04-20 23:37     ` Joel Brobecker
2012-04-24 19:44     ` Maciej W. Rozycki
2012-08-19 22:19       ` Andrew Pinski
2012-08-23 16:27         ` Tom Tromey [this message]
2012-08-23 20:43           ` Andrew Pinski
2012-08-24 13:57             ` Tom Tromey

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=87d32hpo9m.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=andrew.pinski@caviumnetworks.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@codesourcery.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