Re: fast_math_flags_set_p vs. set_fast_math_flags inconsistency?

2020-01-21 Thread Ulrich Weigand
Joseph Myers wrote: > On Mon, 20 Jan 2020, Ulrich Weigand wrote: > > > This has the effect that e.g. after > > > > -ffast-math -fno-finite-math-only > > > > the __FAST_MATH__ macro is no longer predefined, but after > > > > -ffast-math -fno-associative-math > > > > the __FAST_MATH__ macro

[PATCH, v2] wwwdocs: e-mail subject lines for contributions

2020-01-21 Thread Richard Earnshaw (lists)
[updated, following some comments from Gerald, main differences are slight tweaks to the html markup and changing "email" to "e-mail"] This patch proposes some new (additional) rules for email subject lines when contributing to GCC. The goal is to make sure that, as far as possible, the subject

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

2020-01-21 Thread Jakub Jelinek
On Tue, Jan 21, 2020 at 02:52:00PM +, Richard Earnshaw (lists) wrote: > [updated, following some comments from Gerald, main differences are > slight tweaks to the html markup and changing "email" to "e-mail"] > > This patch proposes some new (additional) rules for email subject lines > when c

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

2020-01-21 Thread Richard Earnshaw (lists)
On 21/01/2020 15:04, Jakub Jelinek wrote: On Tue, Jan 21, 2020 at 02:52:00PM +, Richard Earnshaw (lists) wrote: [updated, following some comments from Gerald, main differences are slight tweaks to the html markup and changing "email" to "e-mail"] This patch proposes some new (additional)

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

2020-01-21 Thread Jakub Jelinek
On Tue, Jan 21, 2020 at 03:33:22PM +, Richard Earnshaw (lists) wrote: > > Some examples would be useful I'd say, e.g. it is unclear in what way you > > want the PR number to be appended, shall it be > > something: whatever words describe it PR12345 > > or > > something: whatever words describe

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

2020-01-21 Thread Richard Earnshaw (lists)
On 21/01/2020 15:39, Jakub Jelinek wrote: On Tue, Jan 21, 2020 at 03:33:22PM +, Richard Earnshaw (lists) wrote: Some examples would be useful I'd say, e.g. it is unclear in what way you want the PR number to be appended, shall it be something: whatever words describe it PR12345 or something:

git: remote: *** The first line of a commit message should be a short description of the change, not a single word.

2020-01-21 Thread Martin Liška
Can you please remove the hook for user branches likes: $ git push origin me/filter-non-common Enumerating objects: 27, done. Counting objects: 100% (27/27), done. Delta compression using up to 16 threads Compressing objects: 100% (14/14), done. Writing objects: 100% (14/14), 1.77 KiB | 1.77 MiB/

Re: git: remote: *** The first line of a commit message should be a short description of the change, not a single word.

2020-01-21 Thread Jonathan Wakely
On Tue, 21 Jan 2020 at 16:03, Martin Liška wrote: > > Can you please remove the hook for user branches likes: > > $ git push origin me/filter-non-common > Enumerating objects: 27, done. > Counting objects: 100% (27/27), done. > Delta compression using up to 16 threads > Compressing objects: 100% (

Re: git: remote: *** The first line of a commit message should be a short description of the change, not a single word.

2020-01-21 Thread Richard Earnshaw (lists)
On 21/01/2020 16:14, Jonathan Wakely wrote: On Tue, 21 Jan 2020 at 16:03, Martin Liška wrote: Can you please remove the hook for user branches likes: $ git push origin me/filter-non-common Enumerating objects: 27, done. Counting objects: 100% (27/27), done. Delta compression using up to 16 th

Re: git: remote: *** The first line of a commit message should be a short description of the change, not a single word.

2020-01-21 Thread Nathan Sidwell
On 1/21/20 11:38 AM, Richard Earnshaw (lists) wrote: On 21/01/2020 16:14, Jonathan Wakely wrote: On Tue, 21 Jan 2020 at 16:03, Martin Liška wrote: Can you please remove the hook for user branches likes: $ git push origin me/filter-non-common Enumerating objects: 27, done. Counting objects: 1

Re: git: remote: *** The first line of a commit message should be a short description of the change, not a single word.

2020-01-21 Thread Richard Earnshaw (lists)
On 21/01/2020 16:43, Nathan Sidwell wrote: On 1/21/20 11:38 AM, Richard Earnshaw (lists) wrote: On 21/01/2020 16:14, Jonathan Wakely wrote: On Tue, 21 Jan 2020 at 16:03, Martin Liška wrote: Can you please remove the hook for user branches likes: $ git push origin me/filter-non-common Enumer

Re: fast_math_flags_set_p vs. set_fast_math_flags inconsistency?

2020-01-21 Thread Joseph Myers
On Tue, 21 Jan 2020, Ulrich Weigand wrote: > It looks like there's multiple cases here. For the two flags > -fassociative-math and -freciprocal-math, it seems to have happened just as > you describe: they were created (split out of -funsafe-math-optimizations) > in commit a1a826110720eda37c73f829

Re: git: remote: *** The first line of a commit message should be a short description of the change, not a single word.

2020-01-21 Thread Jason Merrill
On Tue, Jan 21, 2020 at 11:52 AM Richard Earnshaw (lists) < richard.earns...@arm.com> wrote: > On 21/01/2020 16:43, Nathan Sidwell wrote: > > On 1/21/20 11:38 AM, Richard Earnshaw (lists) wrote: > >> On 21/01/2020 16:14, Jonathan Wakely wrote: > >>> On Tue, 21 Jan 2020 at 16:03, Martin Liška wrot

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

2020-01-21 Thread Jason Merrill
On 1/21/20 10:40 AM, Richard Earnshaw (lists) wrote: On 21/01/2020 15:39, Jakub Jelinek wrote: On Tue, Jan 21, 2020 at 03:33:22PM +, Richard Earnshaw (lists) wrote: Some examples would be useful I'd say, e.g. it is unclear in what way you want the PR number to be appended, shall it be some

Re: git: remote: *** The first line of a commit message should be a short description of the change, not a single word.

2020-01-21 Thread Jonathan Wakely
On Tue, 21 Jan 2020 at 17:06, Jason Merrill wrote: > > On Tue, Jan 21, 2020 at 11:52 AM Richard Earnshaw (lists) < > richard.earns...@arm.com> wrote: > > > On 21/01/2020 16:43, Nathan Sidwell wrote: > > > On 1/21/20 11:38 AM, Richard Earnshaw (lists) wrote: > > >> On 21/01/2020 16:14, Jonathan Wak

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

2020-01-21 Thread Richard Earnshaw (lists)
On 21/01/2020 17:20, Jason Merrill wrote: On 1/21/20 10:40 AM, Richard Earnshaw (lists) wrote: On 21/01/2020 15:39, Jakub Jelinek wrote: On Tue, Jan 21, 2020 at 03:33:22PM +, Richard Earnshaw (lists) wrote: Some examples would be useful I'd say, e.g. it is unclear in what way you want the

[PATCH] wwwdocs: document scripts to access personal and vendor spaces

2020-01-21 Thread Richard Earnshaw (lists)
This patch documents some of the scripts that I've published for managing the personal and vendor spaces on the server. It also covers some of the other features that those scripts enable, so that it's all in one place. This is a complete rewrite of the material I had written previously since

Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions

2020-01-21 Thread Segher Boessenkool
Hi! Thanks for doing this. On Tue, Jan 21, 2020 at 02:52:00PM +, Richard Earnshaw (lists) wrote: > This patch proposes some new (additional) rules for email subject lines > when contributing to GCC. The goal is to make sure that, as far as > possible, the subject for a patch will form a good

Re: git: remote: *** The first line of a commit message should be a short description of the change, not a single word.

2020-01-21 Thread Martin Liška
On 1/21/20 6:30 PM, Jonathan Wakely wrote: Whether they make it to trunk or not doesn't really change the fact that a one-word message is poor. If it's only on your local machine, do what you like. The hook only complains when such a commit is published on gcc.gnu.org. I would disagree here. I

What needs to be satisfied to become a type qualifier in standard?

2020-01-21 Thread Akshat Garg
Hello everyone, I am trying to see how a new type qualifier only for pointer variables is suitable to be in standard semantically. I have this thread ( https://gcc.gnu.org/ml/gcc-patches/2019-08/msg02015.html ) where Joseph discussed a bit about what a new type qualifier should satisfy. Can somebo