public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: nick clifton <nickc@redhat.com>
Cc: bernds@codesourcery.com, jzhang918@gmail.com,  gcc-patches@gcc.gnu.org
Subject: Re: Commit: BFIN: Fix use of VEC_last macro in bfin.c
Date: Fri, 17 Aug 2012 12:38:00 -0000	[thread overview]
Message-ID: <502E3B19.8000201@google.com> (raw)
In-Reply-To: <502DEE75.5030706@redhat.com>

On 12-08-17 03:10 , nick clifton wrote:
> Hi Diego,
>> Thanks Nick.  I made the wrong fix here, sorry about that.  I will be
>> making more changes to VEC_ shortly.  What's a good way for me to test
>> them?
>
> All I was doing was building a variety of targets, just to make sure
> that a local, generic patch of my own did not break anything.  If you
> have the disk space then you could try doing the same yourself.

This is great.  Thanks!  Often the problem I have is that I don't know 
what target triplets to use.  We do not have a cheat sheet handy.

Would it be too much imposition for you to put this on the wiki?  This 
is useful for those patches that need to touch files that are only built 
for particular targets.  Often, I don't really need to build the whole 
thing, I just need to know that the target files compile.


Thanks.  Diego.

  reply	other threads:[~2012-08-17 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  9:55 Nick Clifton
2012-08-16 12:15 ` Diego Novillo
2012-08-17  7:17   ` nick clifton
2012-08-17 12:38     ` Diego Novillo [this message]
2012-08-17 13:04       ` nick clifton
2012-08-17 14:53       ` Joseph S. Myers
2012-08-17 15:01         ` Diego Novillo
2012-08-19 17:31           ` Gerald Pfeifer

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=502E3B19.8000201@google.com \
    --to=dnovillo@google.com \
    --cc=bernds@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jzhang918@gmail.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).