public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@gnu.org>
To: Richard Henderson <rth@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	Petr Salinger <Petr.Salinger@seznam.cz>,
		gcc-patches@gcc.gnu.org, Jan Hubicka <jh@suse.cz>,
	Uros Bizjak <ubizjak@gmail.com>
Subject: Re: PING^3 [PATCH] Support for AMD64 targets running GNU/kFreeBSD
Date: Fri, 10 Jun 2011 23:48:00 -0000	[thread overview]
Message-ID: <BANLkTi=n0j6swFVMDaW6932qrYcbUBBB0A@mail.gmail.com> (raw)
In-Reply-To: <4DF28753.4000008@redhat.com>

2011/6/10 Richard Henderson <rth@redhat.com>:
> On 06/10/2011 01:59 PM, Robert Millan wrote:
>> 2011-06-02  Robert Millan  <rmh@gnu.org>
>>
>>       * config/i386/kfreebsd-gnu.h: Resync with `config/i386/linux.h'.
>>       * config/kfreebsd-gnu.h (GNU_USER_DYNAMIC_LINKER): Resync with
>>       `config/linux.h'.
>>
>>       * config/i386/kfreebsd-gnu64.h: New file.
>>       * config.gcc (x86_64-*-kfreebsd*-gnu): Replace `i386/kfreebsd-gnu.h'
>>       with `i386/kfreebsd-gnu64.h'.
>>
>>       * config/i386/linux64.h (GNU_USER_LINK_EMULATION32)
>>       (GNU_USER_LINK_EMULATION64): New macros.
>>       * config/i386/gnu-user64.h (LINK_SPEC): Rely on
>>       `GNU_USER_LINK_EMULATION32' and `GNU_USER_LINK_EMULATION64' instead
>>       of hardcoding `elf_i386' and `elf_x86_64'.
>
> Ok.

Thanks.  Please could you commit?  I don't have write-after-approval perms.

-- 
Robert Millan

      reply	other threads:[~2011-06-10 22:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10 22:04 Robert Millan
2011-06-10 22:51 ` Richard Henderson
2011-06-10 23:48   ` Robert Millan [this message]

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='BANLkTi=n0j6swFVMDaW6932qrYcbUBBB0A@mail.gmail.com' \
    --to=rmh@gnu.org \
    --cc=Petr.Salinger@seznam.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jh@suse.cz \
    --cc=joseph@codesourcery.com \
    --cc=rth@redhat.com \
    --cc=ubizjak@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).