public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Magnus Granberg <zorry@gentoo.org>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: PING^3: [PATCH]: New configure options that make the compiler use -fPIE and -pie as default option
Date: Tue, 19 May 2015 15:33:00 -0000	[thread overview]
Message-ID: <CAMe9rOqncLsJhb7Fhr3t3acDO+Kq38AeA+ac1TKt6oqWwGz-5Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1505191520110.32308@digraph.polyomino.org.uk>

On Tue, May 19, 2015 at 8:21 AM, Joseph Myers <joseph@codesourcery.com> wrote:
> On Mon, 18 May 2015, H.J. Lu wrote:
>
>> > Have updates for all affected specs for all targets been posted?  I just
>> > saw a small and apparently arbitrary subset of targets with patches, and
>> > no explanation of how those targets were identified or why the other
>> > targets with specs mentioning the options in question did not need
>> > updates.
>> >
>>
>> I only posted patches for an  arbitrary subset of targets because
>>
>> 1. Not everyone is interested in --enable-default-pie.
>> 2. I can't tests all targets myself.
>>
>> If patches for all targets is the only blocker before the patch
>> will be approved or target maintainers will help me test the patch,
>> I will post patches for each target affected.
>
> I think the whole thing should be posted as one patch, with both the
> target-independent changes and the target-specific changes for all
> targets.
>

That is what makes me concerned.  I have some simple target-specified
patches which weren't reviewed for years. What will happen if no one
reviews some simple target-specified changes due to

1. Reviewers don't have access to those targets.
2. Target maintainers aren't review them.
3. There are no clear maintainers for those targets.

As the result, my patch may go nowhere.

-- 
H.J.

  reply	other threads:[~2015-05-19 15:27 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 17:31 H.J. Lu
2015-03-06 20:22 ` Magnus Granberg
2015-03-06 20:25   ` H.J. Lu
2015-05-07 21:17 ` Joseph Myers
2015-05-08 17:35   ` H.J. Lu
2015-05-18 22:53     ` Magnus Granberg
2015-05-19  1:25       ` Joseph Myers
2015-05-19  1:34         ` H.J. Lu
2015-05-19 15:27           ` Joseph Myers
2015-05-19 15:33             ` H.J. Lu [this message]
2015-05-19 15:33               ` Paul_Koning
2015-05-19 15:43                 ` H.J. Lu
2015-05-19 15:37               ` Joseph Myers
2015-05-19 19:33                 ` H.J. Lu
2015-05-20 21:29                   ` Joseph Myers
2015-05-20 23:01                   ` Hans-Peter Nilsson
2015-05-20 23:54                     ` H.J. Lu
2015-05-21 14:42                   ` Rainer Orth
2015-05-21 17:19                     ` Joseph Myers
2015-05-21 17:57                     ` H.J. Lu
2015-06-03 12:48                       ` Rainer Orth
     [not found]                   ` <CAMe9rOpZow4w3zcycLoTb5LZdLKP2QWNpsU5oLMJCyZGUTd1fg@mail.gmail.com>
     [not found]                     ` <87vbflkh05.fsf@igel.home>
     [not found]                       ` <CAMe9rOr0SApdtzeOrc-uNDRH8=z6c4EzHUkyXmERW_q9BYjrAQ@mail.gmail.com>
     [not found]                         ` <87k2w1k54t.fsf@igel.home>
2015-05-22 15:39                           ` Fwd: " H.J. Lu
2015-05-26 22:42                             ` Bill Schmidt
2015-05-26 22:53                               ` Bill Schmidt
2015-05-27 15:42                                 ` Peter Bergner
2015-05-27 15:59                                   ` H.J. Lu
2015-05-27 16:17                                     ` Peter Bergner
2015-05-27 16:34                                       ` H.J. Lu
2015-05-27 17:43                                         ` David Edelsohn
2015-05-27 17:44                                           ` H.J. Lu
2015-05-30 15:45                             ` Andreas Schwab
2015-05-30 16:24                               ` H.J. Lu
2015-05-30 16:44                                 ` Andreas Schwab
2015-05-30 17:04                                   ` H.J. Lu
2015-05-30 20:08                                     ` Andreas Schwab
2015-05-30 21:42                                       ` H.J. Lu
2015-05-31  0:52                                         ` Andreas Schwab
2015-05-31  7:13                                           ` H.J. Lu
2015-05-31  8:23                                             ` Andreas Schwab
2015-05-31 15:52                                               ` H.J. Lu
2015-05-30 20:04                             ` Andreas Schwab
2015-05-30 21:08                               ` Andreas Schwab
2015-10-23 11:57                             ` Marcus Shawcroft
2015-10-23 12:44                               ` H.J. Lu
2015-10-23 14:27                                 ` Marcus Shawcroft
2015-10-28 16:06                                 ` Marcus Shawcroft
2015-10-29 11:02                                 ` Richard Earnshaw
2015-10-29 11:18                                   ` H.J. Lu
2015-06-10 13:26                   ` Rainer Orth
2015-05-26 23:09     ` Matthew Fortune
2015-05-27  2:49       ` Matthew Fortune
2015-05-27  4:59       ` H.J. Lu

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=CAMe9rOqncLsJhb7Fhr3t3acDO+Kq38AeA+ac1TKt6oqWwGz-5Q@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=zorry@gentoo.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).