Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Alan Modra
On Fri, Feb 07, 2020 at 10:08:25AM +, Jonathan Wakely wrote: > With Git you can't really have unwanted local commits present in a > tree if you use a sensible workflow, so if you tested in a tree that > was at commit 1234abcd and you push from another machine that is at > the same commit, you k

gcc-8-20200207 is now available

2020-02-07 Thread gccadmin
Snapshot gcc-8-20200207 is now available on https://gcc.gnu.org/pub/gcc/snapshots/8-20200207/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 8 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Tom Tromey
> "Jason" == Jason Merrill writes: Jason> I omit ChangeLogs by adding ':!*/ChangeLog' to the end of the git Jason> send-email command. I don't remember where I found that incantation. Cool, I did not know about this. FWIW if you have the ChangeLog merger available, it's actually more conve

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Jason Merrill
On Fri, Feb 7, 2020 at 1:44 PM Tom Tromey wrote: > > > "Jonathan" == Jonathan Wakely writes: > > Jonathan> I have a script that does the opposite, which I've been using for > Jonathan> years. I edit the ChangeLog files as before, and a Git > Jonathan> prepare-commit-msg hook extracts the top

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Tom Tromey
> "Jonathan" == Jonathan Wakely writes: Jonathan> I have a script that does the opposite, which I've been using for Jonathan> years. I edit the ChangeLog files as before, and a Git Jonathan> prepare-commit-msg hook extracts the top changelog entry from each Jonathan> file in the commit and pr

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Segher Boessenkool
On Fri, Feb 07, 2020 at 03:43:05PM +, Richard Earnshaw (lists) wrote: > On 07/02/2020 15:32, Segher Boessenkool wrote: > >On Fri, Feb 07, 2020 at 01:56:08PM +, Richard Earnshaw (lists) wrote: > >>Any script should, in addition to extracting the author and email also > >>grep for "Co-authore

Re: Matching and testing against smulhsm3

2020-02-07 Thread Segher Boessenkool
Hi! On Fri, Feb 07, 2020 at 03:41:25PM +0100, m wrote: > ...so I tried to write a corresponding matching pattern, like so: > >   (define_insn "smulhshi3" >     [(set (match_operand:HI 0 "register_operand" "=r") >   (truncate:HI >     (ashiftrt:SI >   (mult:SI >     (sign_e

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Richard Earnshaw (lists)
On 07/02/2020 15:32, Segher Boessenkool wrote: On Fri, Feb 07, 2020 at 01:56:08PM +, Richard Earnshaw (lists) wrote: On 07/02/2020 13:48, Segher Boessenkool wrote: Should we require some simple markup in the commit message before the changelogs? Maybe CL gcc/ * blablalba etc. CL g

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Segher Boessenkool
On Fri, Feb 07, 2020 at 01:56:08PM +, Richard Earnshaw (lists) wrote: > On 07/02/2020 13:48, Segher Boessenkool wrote: > >Should we require some simple markup in the commit message before the > >changelogs? Maybe > > > >CL gcc/ > > * blablalba etc. > >CL gcc/testsuite/ > > * gcc.target

Matching and testing against smulhsm3

2020-02-07 Thread m
Hello! I am trying to implement the following insns for my back end: smulhssi3, smulhshi3, smulhsqi3 According to [1], the operation should be equivalent to:   narrow op0, op1, op2;   op0 = (narrow) (((wide) op1 * (wide) op2) >> (N / 2 - 1)); ...so I tried to write a corresponding matching p

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Richard Earnshaw (lists)
On 07/02/2020 13:48, Segher Boessenkool wrote: Hi! On Fri, Feb 07, 2020 at 10:19:56AM +0100, Richard Biener wrote: On Thu, Feb 6, 2020 at 11:25 PM Segher Boessenkool wrote: Yeah, don't look at me then :-) I *like* having most of those steps, most of this should only be done by people who are

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Segher Boessenkool
Hi! On Fri, Feb 07, 2020 at 10:19:56AM +0100, Richard Biener wrote: > On Thu, Feb 6, 2020 at 11:25 PM Segher Boessenkool > wrote: > > Yeah, don't look at me then :-) > > > > I *like* having most of those steps, most of this should only be done by > > people who are awake. > > > > > it's definitel

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Jonathan Wakely
;s easier to not realise exactly what you're testing, it's harder to verify that what you tested is what you eventually pushed). Applying somebody else's patch to test it can be done in a local branch and committed locally. You can always delete that branch later to clear up (a na

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-07 Thread Richard Biener
On Thu, Feb 6, 2020 at 11:25 PM Segher Boessenkool wrote: > > On Thu, Feb 06, 2020 at 03:01:20PM +0100, Richard Biener wrote: > > On Thu, Feb 6, 2020 at 2:51 PM Segher Boessenkool > > wrote: > > > If you rebase changelog files, then yes, it's a bloody pain ;-) > > > > So do you have a script that