public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Svante Signell <svante.signell@gmail.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org,
	Samuel Thibault <samuel.thibault@gnu.org>,
		Matthias Klose	 <doko@debian.org>
Subject: Re: Please include ada-hurd.diff upstream (try2)
Date: Wed, 16 Mar 2016 10:41:00 -0000	[thread overview]
Message-ID: <1458124921.21760.10.camel@gmail.com> (raw)
In-Reply-To: <1892980.xfHAqQvLqb@polaris>

On Wed, 2016-03-16 at 11:08 +0100, Eric Botcazou wrote:
> > 
> > Maybe the time has come now for a proper inclusion of Ada/Gnat support in
> > gcc-* for GNU/Hurd. (Yes, I commit to maintain Ada in gcc for GNU/Hurd in
> > the foreseeable future, according to my abilities).
> > 
> > Attached is an updated patch, now living e.g. in GNU/Debian versions of
> > gcc-5 and gcc-6.
> > 
> > Please tell me if you need a changelog entry too. And yes, I have already
> > signed all copyright papers for FSF wrt gcc (and other packages).
> Yes, patches need ChangeLog.  This one is small though so I have applied it:
> 
> 2016-03-16  Svante Signell  <svante.signell@gmail.com>
> 
>         * gcc-interface/Makefile.in: Add support for x86 GNU/Hurd.
>         * s-osinte-gnu.ads: New file.

Hi Eric,

Sorry for not supplying a ChangeLog yet, I've been busy lately with other
things. Since there is another new file s-osinte-gnu.adb in the latest patch,
that might be added too.

2016-03-16  Svante Signell  <svante.signell@gmail.com>

	* gcc-interface/Makefile.in: Add support for x86 GNU/Hurd.
	* s-osinte-gnu.ads: New specification file.
	* s-osinte-gnu.adb: New body file, basically s-osinte-posix.adb
          adding dummy implementation of functions not yet implemented.

Thanks!

  reply	other threads:[~2016-03-16 10:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 23:42 Svante Signell
2016-03-07  5:22 ` Matthias Klose
2016-03-16 10:08 ` Eric Botcazou
2016-03-16 10:41   ` Svante Signell [this message]
2016-03-16 10:54     ` Eric Botcazou
2016-03-16 11:15       ` Svante Signell
2016-03-16 11:19         ` Arnaud Charlet
2016-03-16 21:55       ` Svante Signell
2016-03-17  7:51         ` Arnaud Charlet
2016-03-31  9:52           ` Svante Signell
2016-04-19  6:49             ` Svante Signell
2016-04-19  8:30               ` Arnaud Charlet
2016-04-25  9:22                 ` Svante Signell
2016-04-25  9:50                   ` Arnaud Charlet
2016-04-25 10:28                     ` Svante Signell
2016-04-25 10:31                       ` Arnaud Charlet
2016-04-27  7:41                       ` Eric Botcazou
2016-04-27  8:06                         ` Svante Signell
2016-05-04 15:29                           ` Samuel Thibault
2016-05-04 15:34                             ` Samuel Thibault
2016-05-04 16:02                               ` Arnaud Charlet
2016-05-04 16:43                               ` Svante Signell
2016-05-04 17:43                                 ` Svante Signell
2016-05-04 21:06                                   ` Samuel Thibault
2016-05-04 21:25                                     ` Svante Signell
2016-05-04 21:28                                       ` Samuel Thibault
2016-05-04 19:17                               ` Eric Botcazou

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=1458124921.21760.10.camel@gmail.com \
    --to=svante.signell@gmail.com \
    --cc=doko@debian.org \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=samuel.thibault@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).