gcc-9-20201106 is now available

2020-11-06 Thread GCC Administrator via Gcc
Snapshot gcc-9-20201106 is now available on https://gcc.gnu.org/pub/gcc/snapshots/9-20201106/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 9 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: gcc/DATESTAMP not updated any longer

2020-11-06 Thread Iain Sandoe via Gcc
Jakub Jelinek via Gcc wrote: On Fri, Nov 06, 2020 at 08:56:25PM +0100, Richard Biener wrote: Darwin: Darwin 20 is to be macOS 11 (Big Sur). So, I'm afraid it must fail or bypass this code path somewhere earlier in the hooks. Is that maybe already known to the repo when it is on some rebase

Re: gcc/DATESTAMP not updated any longer

2020-11-06 Thread Jakub Jelinek via Gcc
On Fri, Nov 06, 2020 at 08:56:25PM +0100, Richard Biener wrote: > >Darwin: Darwin 20 is to be macOS 11 (Big Sur). > >So, I'm afraid it must fail or bypass this code path somewhere earlier > >in the hooks. > > Is that maybe already known to the repo when it is on some rebased user > branch? I

Re: gcc/DATESTAMP not updated any longer

2020-11-06 Thread Richard Biener via Gcc
On November 6, 2020 8:45:55 PM GMT+01:00, Jakub Jelinek via Gcc wrote: >On Tue, Nov 03, 2020 at 06:26:58PM +, Joseph Myers wrote: >> On Mon, 2 Nov 2020, Jakub Jelinek via Gcc wrote: >> >> > It isn't that easy (because update_version_git checks the gcc trunk >and >> > so I had to insert a sh

Re: gcc/DATESTAMP not updated any longer

2020-11-06 Thread Jakub Jelinek via Gcc
On Tue, Nov 03, 2020 at 06:26:58PM +, Joseph Myers wrote: > On Mon, 2 Nov 2020, Jakub Jelinek via Gcc wrote: > > > It isn't that easy (because update_version_git checks the gcc trunk and > > so I had to insert a sh invocation in which I've tweaked it), but it worked, > > thanks. But something

Re: Dead Field Elimination and Field Reordering

2020-11-06 Thread Erick Ochoa
Hi Richard, just some top-level comments before I write about anything specific: * I have removed all non-essential flags I introduced * I have placed the standard headers before config * I have squashed some changes that I sent to the patches mailing list and make sure that the transformation

Re: Symbol + Constant output.

2020-11-06 Thread Iain Sandoe
Hi, Hongyu Wang via Gcc wrote: I've adjust the testcase and now it only contains constant offset, since with -fPIC the mov target address does not contain any symbol in the assembler. Could you help to check the attached changes on darwin and see if they all get passed? LGTM. OK from a