From: Joseph Myers <joseph@codesourcery.com>
To: Martin Sebor <msebor@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Marek Polacek <polacek@redhat.com>,
Jason Merrill <jason@redhat.com>, Nathan Sidwell <nathan@acm.org>,
Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] accept all C integer types in function parameters referenced by alloc_align (PR 88363)
Date: Tue, 11 Dec 2018 18:16:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1812111812230.25086@digraph.polyomino.org.uk> (raw)
In-Reply-To: <78a7396e-8a64-4919-82d6-38959fda0e55@gmail.com>
On Tue, 11 Dec 2018, Martin Sebor wrote:
> I recently brought up the question of the write w/o approval
> policy on the gcc list:
>
> https://gcc.gnu.org/ml/gcc/2018-11/msg00165.html
>
> looking for clarification. Except for Jeff's comment (which
> I'm afraid didn't really clarify things), didn't get any.
I think "will the person who objects to my work the most be able to find a
fault with my fix?" in the policy on obviousness is clear enough. A
policy decision on what is or is not part of a language extension can't be
obvious, and nor can determining subtle questions of exactly what the
definition of some internal interface is or should be.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-12-11 18:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 23:30 Martin Sebor
2018-12-11 7:17 ` Jakub Jelinek
2018-12-11 15:14 ` Jason Merrill
2018-12-11 15:43 ` Marek Polacek
2018-12-11 16:59 ` Martin Sebor
2018-12-11 18:15 ` Marek Polacek
2018-12-11 19:43 ` Martin Sebor
2018-12-11 18:16 ` Joseph Myers [this message]
2018-12-11 19:46 ` Martin Sebor
2018-12-11 20:09 ` Jason Merrill
2018-12-11 20:37 ` Martin Sebor
2018-12-11 20:48 ` Jakub Jelinek
2018-12-11 22:46 ` Martin Sebor
2018-12-11 22:52 ` Marek Polacek
2018-12-11 23:08 ` Martin Sebor
2018-12-11 23:19 ` Jason Merrill
2018-12-18 21:42 ` Martin Sebor
2019-01-03 22:12 ` PING #2 " Martin Sebor
2019-01-04 20:56 ` Joseph Myers
2019-01-06 10:27 ` Jakub Jelinek
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=alpine.DEB.2.21.1812111812230.25086@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=msebor@gmail.com \
--cc=nathan@acm.org \
--cc=polacek@redhat.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).