public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: Jean Christophe Beyler <jean.christophe.beyler@gmail.com>
Cc: Ian Lance Taylor <iant@google.com>, gcc@gcc.gnu.org
Subject: Re: Adding constraints.md to my port
Date: Wed, 15 Jul 2009 05:30:00 -0000	[thread overview]
Message-ID: <4A5D6965.7060907@gnu.org> (raw)
In-Reply-To: <c568a2600907141331r4bd5b7e4jb5083fbc68d6d435@mail.gmail.com>

On 07/14/2009 10:31 PM, Jean Christophe Beyler wrote:
> Ok, so actually, my cpu.h file had some of those included. I've
> removed them and am now filling in the constraints.md file with what
> is needed. I also so that they were obsolete in the GCC internals,
> I'll be moving everything to the constraints then.

That's good, it's usually much more readable.  However, as you found 
out, it's an "all or nothing" decision for each port.

Paolo

  reply	other threads:[~2009-07-15  5:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 18:30 Jean Christophe Beyler
2009-07-14 19:53 ` Ian Lance Taylor
2009-07-14 20:31   ` Jean Christophe Beyler
2009-07-15  5:30     ` Paolo Bonzini [this message]
2009-07-15 15:22       ` Jean Christophe Beyler

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=4A5D6965.7060907@gnu.org \
    --to=bonzini@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=jean.christophe.beyler@gmail.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).