Re: Incremental updating of SSA_NAMEs that are passed to b_c_p

2020-10-28 Thread Richard Biener via Gcc
On Tue, Oct 27, 2020 at 7:36 PM Ilya Leoshkevich via Gcc wrote: > > Hi, > > I'd like to revive the old discussion regarding the interaction of > jump threading and b_c_p causing the latter to incorrectly return 1 in > certain cases: > > https://gcc.gnu.org/pipermail/gcc-patches/2020-June/547236.ht

GCC 10 and Coverity Scan

2020-10-28 Thread Joel Sherrill
parc-rtems6-gcc (GCC) 10.2.1 20201028 (RTEMS 6, RSB 4c5af1f7c1553e53739ca4e9892de26924ec2b3f, Newlib fcaaf40) I am a bit suspicious that Coverity isn't handling the transition from 1 to 2 digits in the major number. All I am changing is the name of the target in the script that does the analysis

Re: GCC 10 and Coverity Scan

2020-10-28 Thread paulf
c-rtems5-gcc (GCC) 7.5.0 20191114 (RTEMS 5, RSB 5 (cbae90a5817a), > Newlib 7947581) > > $ sparc-rtems6-gcc --version > sparc-rtems6-gcc (GCC) 10.2.1 20201028 (RTEMS 6, RSB > 4c5af1f7c1553e53739ca4e9892de26924ec2b3f, Newlib fcaaf40) Hi Putting aside politics (I used to work for Synopsys

Re: gsi_remove on a call

2020-10-28 Thread Gary Oblock via Gcc
Martin, After some digging and a little luck, I found that this does what I wanted: cgraph_update_edges_for_call_stmt ( stmt, gimple_call_fndecl ( stmt), NULL); Thanks, Gary From: Martin Jambor Sent: Tuesday, October 27, 2020 5:44 AM To: Gary Oblock ; gcc@gcc.g

[1-800-GIT-HELP] Pushing a merge with master to a branch fails with git gcc-verify

2020-10-28 Thread Thomas Koenig via Gcc
I tried to update the coarray_native branch to current master with "git merge master" as given by https://gcc.gnu.org/gitwrite.html#branches That worked without any error message. Next, I tried to verify that a "git push" would succeed, and got an error: $ git gcc-verify Checking bf6dad60c338a

Re: [1-800-GIT-HELP] Pushing a merge with master to a branch fails with git gcc-verify

2020-10-28 Thread Andre Vehreschild
Hi Thomas, at work we usually do not merge master back into a dev branch, but use 'git rebase -i master'. This will so to say stash any commits on the dev-branch, i.e. roll it back, then apply all changes of master and then apply the stashed changes again. This should allow to bypass any server s

Top Website & Mobile App Design and Development

2020-10-28 Thread Rona via Gcc
Hi gcc@gcc.gnu.org, This is Rona, From India, hope you are fine. We are an app development and web design company that turns ideas into exceptional solutions. We are offering: . Native Applications . Android & iOS Apps . Custom Web Design . Website deve

Re: [1-800-GIT-HELP] Pushing a merge with master to a branch fails with git gcc-verify

2020-10-28 Thread Iain Sandoe via Gcc
Thomas Koenig via Gcc wrote: I tried to update the coarray_native branch to current master with "git merge master" as given by https://gcc.gnu.org/gitwrite.html#branches That worked without any error message. Next, I tried to verify that a "git push" would succeed, and got an error: $ git g

Re: [1-800-GIT-HELP] Pushing a merge with master to a branch fails with git gcc-verify

2020-10-28 Thread Jakub Jelinek via Gcc
On Wed, Oct 28, 2020 at 06:53:35PM +0100, Thomas Koenig via Gcc wrote: > I tried to update the coarray_native branch to current master with > "git merge master" as given by > > https://gcc.gnu.org/gitwrite.html#branches > > That worked without any error message. > > Next, I tried to verify that

Re: [1-800-GIT-HELP] Pushing a merge with master to a branch fails with git gcc-verify

2020-10-28 Thread Thomas Koenig via Gcc
Hi, Don't use git gcc-verify for development branches or user branches, it checks the rules required for release branches and the trunk only. Other branches have different rules. Thanks to everybody for their help. I have now pushed the merge to the branch successfully. I'm glad that the par