Aliasing rules for unannotated SYMBOL_REFs

TL;DR: if we have two bare SYMBOL_REFs X and Y, neither of which have an associated source-level decl and neither of which are in an anchor block: (Q1) can a valid byte access at X+C alias a valid byte access at Y+C? (Q2) can a valid byte access at X+C1 alias a valid byte access at Y+C2, C1

musl, glibc and ideal place for __stack_chk_fail_local

[ sending it to musl, glibc and gcc devel mailing list as we need to build a consensus across the projects ] To support smash stack protection gcc emits __stack_chk_fail calls on all targets. On top of that gcc emits __stack_chk_fail_local calls at least on i386 and powerpc: https://bugs.gen

Git push account

Which account should I use to push my local patch to git repo of gcc? I have a sourceware account that works for svn, but now it doesn't for git. Actually both below commands were tried, but failed. git push ssh://f...@sourceware.org/gcc/gcc.git ..., git push ssh://f...@gcc.gnu.org/gcc/gcc.gi

Re: Git push account

On Jan 25 2020, Feng Xue OS wrote: > Which account should I use to push my local patch to git repo of gcc? See . > I have a sourceware account that works for svn, but now it doesn't for git. > Actually both below commands were tried, but failed. >

Re: Git push account

Thanks. Feng From: Andreas Schwab Sent: Saturday, January 25, 2020 10:07 PM To: Feng Xue OS Cc: gcc@gcc.gnu.org Subject: Re: Git push account On Jan 25 2020, Feng Xue OS wrote: > Which account should I use to push my local patch to git repo of gcc? See

Re: Git ChangeLog policy for GCC Testsuite inquiry

On 1/24/20 4:36 PM, Jeff Law wrote: On Fri, 2020-01-24 at 20:32 +0100, Eric Botcazou wrote: I strongly prefer to move towards relying on the git log. In my experience the output of git log is a total mess so cannot replace ChangeLogs. But we can well decide to drop ChangeLog for the testsuite

Re: [musl] musl, glibc and ideal place for __stack_chk_fail_local

On Sat, Jan 25, 2020 at 10:53:31AM +, Sergei Trofimovich wrote: > [ sending it to musl, glibc and gcc devel mailing list as we need > to build a consensus across the projects ] > > To support smash stack protection gcc emits __stack_chk_fail > calls on all targets. On top of that gcc emits _

Re: Git ChangeLog policy for GCC Testsuite inquiry

On Sat, 2020-01-25 at 10:50 -0500, Nathan Sidwell wrote: > On 1/24/20 4:36 PM, Jeff Law wrote: > > On Fri, 2020-01-24 at 20:32 +0100, Eric Botcazou wrote: > > > > I strongly prefer to move towards relying on the git log. > > > > > > In my experience the output of git log is a total mess so cannot

Re: Git push account

On Sat, 2020-01-25 at 12:39 +, Feng Xue OS wrote: > Which account should I use to push my local patch to git repo of gcc? > I have a sourceware account that works for svn, but now it doesn't for git. > Actually both below commands were tried, but failed. > git push ssh://f...@sourceware.org/

gcc-9-20200125 is now available

Snapshot gcc-9-20200125 is now available on https://gcc.gnu.org/pub/gcc/snapshots/9-20200125/ 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