From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@foss.arm.com>,
Jiong Wang <jiong.wang@foss.arm.com>,
Bernd Schmidt <bschmidt@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: PING: [PATCH] PR target/67215: -fno-plt needs improvements for x86
Date: Thu, 29 Oct 2015 01:11:00 -0000 [thread overview]
Message-ID: <CAMe9rOpcPHqyjKr-8UWCZLjbhwqosm1B=D5J2P7qxpgAgoqSyg@mail.gmail.com> (raw)
In-Reply-To: <563166EC.8050903@redhat.com>
On Wed, Oct 28, 2015 at 5:23 PM, Jeff Law <law@redhat.com> wrote:
> On 10/27/2015 12:54 PM, H.J. Lu wrote:
>>>>
>>>> HJ, Thanks for committing the change even when we were discussing the
>>>> change
>>>
>>>
>>> This is what I'm primarily concerned about.
>>>
>>> Bernd's message was pretty clear in my mind:
>>>
>>> https://gcc.gnu.org/ml/gcc-patches/2015-10/msg02861.html
>>>
>>> It was conditional approval based on no other target using -fno-plt and
>>> agreement from the x86 maintainers.
>>>
>>> HJ replied that aarch64 uses -fno-plt:
>>>
>>>
>>> https://gcc.gnu.org/ml/gcc-patches/2015-10/msg02865.html
>>>
>>>
>>> And then apparently HJ committed the patch.
>>>
>>>
>>> commit 47b727e5ec3f6f4f0a30ee899adce80185ad6999
>>> Author: hjl <hjl@138bc75d-0d04-0410-961f-82ee72b054a4>
>>> Date: Tue Oct 27 14:29:31 2015 +0000
>>>
>>> When reviewers conditionally approve a patch, the conditions need to be
>>> satisfied before a patch can be committed. Ignoring the conditions seems
>>> like a significant breech of trust to me.
>>>
>>> HJ, why did you commit the patch given it didn't meet the conditions
>>> Bernd
>>> set forth for approval?
>>>
>>
>> Sorry for the trouble my patch caused. The bug is in aarch64 backend.
>
> You didn't answer my question.
>
> I asked why you committed a patch given it didn't meet the conditions Bernd
> set forth for approval. I didn't ask anything about the bug itself.
>
> So I'll ask again, why did you commit a patch which you clearly knew did not
> meet the conditions Bernd set forth for approval?
I believed that aarch64 backend didn't properly handle -fno-plt,
which shouldn't block my patch.
--
H.J.
next prev parent reply other threads:[~2015-10-29 1:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 19:59 H.J. Lu
2015-10-27 11:28 ` Bernd Schmidt
2015-10-27 11:38 ` H.J. Lu
2015-10-27 12:52 ` Uros Bizjak
2015-10-27 12:57 ` Jiong Wang
2015-10-27 13:07 ` H.J. Lu
2015-10-27 13:55 ` Jiong Wang
2015-10-27 14:49 ` Ramana Radhakrishnan
2015-10-27 15:20 ` H.J. Lu
2015-10-27 15:27 ` Jiong Wang
2015-10-27 15:33 ` H.J. Lu
2015-10-27 17:53 ` Jeff Law
2015-10-27 15:45 ` Ramana Radhakrishnan
2015-10-27 17:50 ` Jeff Law
2015-10-27 19:31 ` H.J. Lu
2015-10-29 1:10 ` Jeff Law
2015-10-29 1:11 ` H.J. Lu [this message]
2015-10-29 1:14 ` Bernd Schmidt
2015-10-29 1:21 ` H.J. Lu
2015-10-29 1:47 ` Bernd Schmidt
2015-10-29 3:39 ` H.J. Lu
2015-10-29 9:46 ` Ramana Radhakrishnan
2015-10-29 17:18 ` Jeff Law
2015-10-29 17:15 ` Jeff Law
2015-12-01 13:38 ` David Edelsohn
2015-10-29 17:08 ` Jeff Law
2015-10-27 21:02 ` Jeff Law
2015-10-28 10:36 ` Ramana Radhakrishnan
2015-10-28 11:01 ` James Greenhalgh
2015-10-28 11:05 ` James Greenhalgh
2015-10-28 14:45 ` Ramana Radhakrishnan
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='CAMe9rOpcPHqyjKr-8UWCZLjbhwqosm1B=D5J2P7qxpgAgoqSyg@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiong.wang@foss.arm.com \
--cc=law@redhat.com \
--cc=ramana.radhakrishnan@foss.arm.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).