Re: Add support to trace comparison instructions and switch statements

2017-07-15 Thread 吴潍浠(此彼)
Hi Implementing __sanitizer_cov_trace_cmp[1248]_const is OK . And I will try to find some determinate way to judge this comparison is for loop or not. Because all the loops(for() or while()) seem to be transformed to "if" and "goto" before running sancov pass. Does it necessary to include APIs

Re: Add support to trace comparison instructions and switch statements

2017-07-15 Thread Dmitry Vyukov via gcc
On Sat, Jul 15, 2017 at 9:21 AM, 吴潍浠(此彼) wrote: > Hi > > Implementing __sanitizer_cov_trace_cmp[1248]_const is OK . > And I will try to find some determinate way to judge this comparison is for > loop or not. > Because all the loops(for() or while()) seem to be transformed to "if" and > "goto" b

Re: gcc-6-branch snapshots disabled?

2017-07-15 Thread Gerald Pfeifer
On Fri, 14 Jul 2017, Mikael Pettersson wrote: > Seems like the weekly snapshots from gcc-6-branch were disabled before > the 6.4.0 release but not re-enabled afterwards. The snapshots from > trunk and gcc-{7,5}-branch are being generated as usual. You are right, I observed the same and just enabl

Re: gcc-6-branch snapshots disabled?

2017-07-15 Thread Mikael Pettersson
Gerald Pfeifer writes: > On Fri, 14 Jul 2017, Mikael Pettersson wrote: > > Seems like the weekly snapshots from gcc-6-branch were disabled before > > the 6.4.0 release but not re-enabled afterwards. The snapshots from > > trunk and gcc-{7,5}-branch are being generated as usual. > > You are

Re: Linux and Windows generate different binaries

2017-07-15 Thread Yuri Gribov
On Fri, Jul 14, 2017 at 8:45 AM, Yuri Gribov wrote: > FWIW I've done a quick analysis of recent gcc source code using > https://github.com/yugr/sortcheck and found lots of comparison > functions which can return 0 for different objects. > > All these may cause arrays to be sorted differently on di

Re: Linux and Windows generate different binaries

2017-07-15 Thread Segher Boessenkool
On Sat, Jul 15, 2017 at 07:40:13PM +0100, Yuri Gribov wrote: > Looked at generators, we have three comparison routines which return 0 > for different objects but all seem to be safe i.e. can't influence > code generated by GCC. > > alt_state_cmp (genautomata.c) - intentional, duplicates are remove

Re: Linux and Windows generate different binaries

2017-07-15 Thread Alexander Monakov
On Fri, 14 Jul 2017, Yuri Gribov wrote: > I've also detect transitiveness violation compare_assert_loc > (tree-vrp.c), will send fix once tests are done. There are more issues still, see the thread starting at https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00899.html Alexander

Re: [patch] RFC: Hook for insn costs?

2017-07-15 Thread Segher Boessenkool
Hi! On Wed, Jul 12, 2017 at 03:15:09PM +0200, Georg-Johann Lay wrote: > the current cost computations in rtlanal.c and maybe other places > suffer from the fact that they are hiding parts of the expressions > from the back-end, like SET_DESTs of single_set or the anatomy of > PARALELLs. > > Would

Remove ca.mirror.babylon.network

2017-07-15 Thread Tim Semeijn
We will soon decommission our Canadian mirror due to restructuring. Please remove the following server from the mirror list: ca.mirror.babylon.network/gcc Our French mirrors will remain active. Thanks! -- Tim Semeijn Babylon Network PGP: 0x2A540FA5 / 3DF3 13FA 4B60 E48A E755 9663 B187 0310 2A

Re: Linux and Windows generate different binaries

2017-07-15 Thread Yuri Gribov
On Sat, Jul 15, 2017 at 10:01 PM, Alexander Monakov wrote: > On Fri, 14 Jul 2017, Yuri Gribov wrote: >> I've also detect transitiveness violation compare_assert_loc >> (tree-vrp.c), will send fix once tests are done. > > There are more issues still, see the thread starting at > https://gcc.gnu.org

Re: Remove ca.mirror.babylon.network

2017-07-15 Thread Gerald Pfeifer
On Sun, 16 Jul 2017, Tim Semeijn wrote: > We will soon decommission our Canadian mirror due to restructuring. > Please remove the following server from the mirror list: > > ca.mirror.babylon.network/gcc Thank for you the head-up, Tim. I applied the patch below to make this change accordingly. >