Wrong insn scheduled by Sched1 pass

2020-11-02 Thread Jojo R
Hi, From origin insn seqs, I think the insn 'r500=unspec[r100] 300’ is in Good place because of the bypass of my pipeline description, it is not needed to schedule. But the result of Sched1 pass schedule it, I check the souce code of sched-rgn.c & haifa-sched.c From compute_priorities() I think

Mail delivery failed: returning message to sender

2020-11-02 Thread Mail Delivery System
This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: gcc@gcc.gnu.org host gcc.gnu.org [8.43.85.97] SMTP error from remote mail serve

Re: gcc/DATESTAMP not updated any longer

2020-11-02 Thread Jakub Jelinek via Gcc
On Mon, Nov 02, 2020 at 09:37:56PM +0100, Martin Liška wrote: > > writing to ./gcc/testsuite/ChangeLog > > empty group "()" found:"* tree-vect-slp.c (): Update backedges in > > single-node cycles." > > Traceback (most recent call last): > >File "../gcc-changelog/git_update_version.py", lin

Re: gcc/DATESTAMP not updated any longer

2020-11-02 Thread Martin Liška
On 11/2/20 8:43 PM, Jakub Jelinek wrote: On Mon, Nov 02, 2020 at 08:14:22PM +0100, Rainer Orth wrote: I noticed that gcc/DATESTAMP isn't updated any longer after this Friday. I doubt this is intentional... === Working on: master === branch pulled and checked out 74 revisions since last Daily

Re: gcc/DATESTAMP not updated any longer

2020-11-02 Thread Jakub Jelinek via Gcc
On Mon, Nov 02, 2020 at 08:14:22PM +0100, Rainer Orth wrote: > I noticed that gcc/DATESTAMP isn't updated any longer after this > Friday. I doubt this is intentional... === Working on: master === branch pulled and checked out 74 revisions since last Daily bump writing to ./libstdc++-v3/ChangeLog

gcc/DATESTAMP not updated any longer

2020-11-02 Thread Rainer Orth
I noticed that gcc/DATESTAMP isn't updated any longer after this Friday. I doubt this is intentional... Rainer -- - Rainer Orth, Center for Biotechnology, Bielefeld University

Re: Symbol + Constant output.

2020-11-02 Thread Uros Bizjak via Gcc
On Sun, Nov 1, 2020 at 2:04 PM Iain Sandoe wrote: > > Hi Uros, > > I was looking into the test fails for the new keylocker-* testcases. > > Many are because of missing “_” (which seems to happen more often than > not). These I can fix trivially. > > But some are because we have: > > name+constant