public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: JonY <10walls@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: GCC maintainer volunteer?
Date: Thu, 21 Feb 2013 21:48:00 -0000	[thread overview]
Message-ID: <51269624.50404@gmail.com> (raw)
In-Reply-To: <20130221165907.GG28458@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]

On 2/22/2013 00:59, Corinna Vinschen wrote:
> On Feb 21 11:31, Chris Sutcliffe wrote:
>> On 21 February 2013 10:38, NightStrike wrote:
>>> On Thu, Feb 21, 2013 at 3:42 AM, Corinna Vinschen wrote:
>>>> On Feb 21 21:33, JonY wrote:
>>>>> On 2/21/2013 20:40, NightStrike wrote:
>>>>>>> I've started looking at the patches, they definitely aren't trivial.
>>>>>>> I'll probably be releasing it as experimental.
>>>>>>
>>>>>> There are local cygwin patches to gcc?
>>>>>>
>>>>>
>>>>> Yes, about 100KB of it. I confess I don't know what most of is for, my
>>>>> understanding of the gcc internals are limited.
>>>>
>>>> I assume some (or all) of them are already upstream, but they were not
>>>> backported into the 4.5.x branch.  It might be a good idea to start out
>>>> with a clean upstream build and then look into the patches if they still
>>>> make some sense.
>>>
>>> Are they in 4.6?  If so, why not just start fresh and clean with a 4.6
>>> 'chain that needs zero patching?
>>
>> I believe Corinna means going to later version of GCC, preferably
>> straight to 4.7 would be great.
> 
> Exactly.  The question is then, what patches from the 4.5.3 gcc were
> not applied upstream and still make sense today.
> 

I have not looked at all the patches closely, but some of them were not
merged in gcc-4.7.2, at least the peflags patch did not.

Who is the upstream GCC maintainer for Cygwin anyway?



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]

  reply	other threads:[~2013-02-21 21:48 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 17:16 Changing dependent library version numbers vs. test packages vs. requires: lines Dave Korn
2012-11-24  5:54 ` marco atzeri
2012-11-24  9:48   ` Corinna Vinschen
2013-01-14 16:50 ` Chris Sutcliffe
2013-01-18 13:32   ` Corinna Vinschen
2013-02-04 10:17     ` Corinna Vinschen
2013-02-18 23:59       ` Chris Sutcliffe
2013-02-19  7:46         ` GCC maintainer volunteer? (was Re: Changing dependent library version numbers vs. test packages vs. requires: lines.) Corinna Vinschen
2013-02-19 10:22           ` JonY
2013-02-19 11:46             ` Yaakov
2013-02-19 12:53               ` JonY
2013-02-21 11:53                 ` JonY
2013-02-21 12:40                   ` NightStrike
2013-02-21 13:34                     ` GCC maintainer volunteer? JonY
2013-02-21 13:42                       ` Corinna Vinschen
2013-02-21 13:47                         ` JonY
2013-02-21 15:39                         ` NightStrike
2013-02-21 16:31                           ` Chris Sutcliffe
2013-02-21 16:59                             ` Corinna Vinschen
2013-02-21 21:48                               ` JonY [this message]
2013-02-21 23:48                                 ` marco atzeri
2013-02-22  5:21                                 ` Christopher Faylor
2013-02-22  8:39                                   ` Corinna Vinschen
2013-02-22  7:31                               ` Yaakov
2013-02-22  8:38                                 ` Corinna Vinschen
2013-02-22  9:18                                 ` JonY
2013-02-23 15:04                                   ` JonY
2013-02-23 15:46                                     ` Ken Brown
2013-02-24  1:12                                       ` JonY
2013-02-24  1:39                                         ` Ken Brown
2013-02-24  2:02                                           ` JonY
2013-02-24  4:55                                             ` Christopher Faylor
2013-02-24  5:22                                               ` Chris Sutcliffe
2013-02-25 14:40                                               ` JonY
2013-02-25 18:22                                                 ` Christopher Faylor
2013-02-27 12:06                                                 ` JonY
2013-02-27 13:11                                                   ` Corinna Vinschen
2013-02-27 13:29                                                     ` JonY
2013-02-27 13:59                                                       ` Corinna Vinschen
2013-02-27 22:24                                                         ` JonY
2013-02-28  0:28                                                           ` marco atzeri
2013-02-28 10:05                                                         ` Yaakov
2013-02-28 17:06                                                           ` NightStrike
2013-02-28 19:44                                                             ` Yaakov
2013-03-06 10:29                                               ` Yaakov
2013-03-06 10:41                                                 ` Corinna Vinschen
2013-03-06 16:14                                                   ` Christopher Faylor

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=51269624.50404@gmail.com \
    --to=10walls@gmail.com \
    --cc=cygwin-apps@cygwin.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).