public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Flavio Cruz <flaviocruz@gmail.com>
Cc: <gcc-patches@gcc.gnu.org>, <bug-hurd@gnu.org>
Subject: Re: [PATCH] Add support for x86_64-*-gnu-* targets to build x86_64 gnumach/hurd
Date: Thu, 26 Jan 2023 09:34:16 +0100	[thread overview]
Message-ID: <87bkmlpud3.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <Y6nbJLinJtSPip+8@mars>

Hi Flavio!

On 2022-12-26T12:34:28-0500, Flavio Cruz via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> Tested by building a toolchain and compiling gnumach for x86_64

Oh, wow, so this is indeed happening, finally!  :-D

> This is the basic version without unwind support which I think is only required to
> implement exceptions.

ACK, this can all be tuned later.  We understand that ABI to be
completely unstable at this point.


Your patch generally looks good, and I'll drop it into my regular
x86_64-pc-linux-gnu testing, to verify that we don't accidentally break
things re 'x86_64-*-gnu*' matching (but I think we're safe).


As you don't have FSF Copyright Assignment on file for GCC (as far as I
can tell), are you either going to get that, or re-submit this patch with
DCO ('Signed-off-by:' tag), <https://gcc.gnu.org/contribute.html#legal>?


While at that, please also adjust:

> --- /dev/null
> +++ b/gcc/config/i386/gnu64.h
> @@ -0,0 +1,40 @@
> +/* Configuration for an x86_64 running GNU with ELF as the target machine.  */
> +
> +/*
> +Copyright (C) 2022 Free Software Foundation, Inc.

^ 2023 ;-)


Grüße
 Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

  parent reply	other threads:[~2023-01-26  8:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Y6DgFCo4mEzztu+Q@mars>
2022-12-26 17:34 ` Flavio Cruz
2023-01-09 18:00   ` Flávio Cruz
2023-01-25 15:56     ` Flávio Cruz
2023-01-26  8:34   ` Thomas Schwinge [this message]
2023-01-27  6:49     ` Flavio Cruz
     [not found]       ` <875ycr1xwp.fsf@dem-tschwing-1.ger.mentorg.com>
     [not found]         ` <CAKwpGPwYX77GbZk=TiD73AFs8+KvQrZ-8nkArQ_H=R9hiC_Pfg@mail.gmail.com>
2023-01-30 15:44           ` Thomas Schwinge
2023-02-01 18:19             ` Jan-Benedict Glaw
2023-02-02  5:55               ` [PATCH] Add x86_64-gnu target to contrib/config-list.mk Flavio Cruz
2023-02-10 10:05                 ` Thomas Schwinge

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=87bkmlpud3.fsf@euler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=bug-hurd@gnu.org \
    --cc=flaviocruz@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).