[Bug tree-optimization/40770] Vectorization of complex types, vectorization of sincos missing

2020-09-22 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40770 --- Comment #25 from 康 珊 --- (In reply to rguent...@suse.de from comment #24) > On September 22, 2020 1:14:48 PM GMT+02:00, kangshan0910 at hotmail dot com > wrote: > >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40770 > >

[Bug tree-optimization/40770] Vectorization of complex types, vectorization of sincos missing

2020-09-22 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40770 --- Comment #23 from 康 珊 --- It seems that gcc will use "_ZGVeN8vl8l8_sincos" which doesn't exit in libmvec. /usr/bin/ld: /tmp/ccTYyEZM.o: in function `main': /home/pnp/ks/test_sincos.c:38: undefined reference to `_ZGVeN8vl8l8_sincos'

[Bug tree-optimization/40770] Vectorization of complex types, vectorization of sincos missing

2020-09-22 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40770 --- Comment #21 from 康 珊 --- (In reply to Jakub Jelinek from comment #15) > OpenMP has a way to express this, > #pragma omp declare simd notinbranch linear(y,z) > double sincos (double x, double *y, double *z); > As can be seen on -O2

[Bug tree-optimization/40770] Vectorization of complex types, vectorization of sincos missing

2020-09-22 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40770 --- Comment #20 from 康 珊 --- Created attachment 49255 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49255=edit test source file

[Bug tree-optimization/40770] Vectorization of complex types, vectorization of sincos missing

2020-09-22 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40770 --- Comment #13 from 康 珊 --- (In reply to Richard Biener from comment #12) > *** Bug 97149 has been marked as a duplicate of this bug. *** Will you look at this?

[Bug c/97149] sincos failed to be vectorized by gcc

2020-09-22 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97149 康 珊 changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #3 from 康 珊 --- (In reply to

[Bug c/97149] sincos failed to be vectorized by gcc

2020-09-21 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97149 --- Comment #1 from 康 珊 --- Created attachment 49247 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49247=edit test source code

[Bug c/97149] New: sincos failed to be vectorized by gcc

2020-09-21 Thread kangshan0910 at hotmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: kangshan0910 at hotmail dot com Target Milestone: --- My code pattern is: for (unsigned int i = 0; i < loopCount; i++) { for (unsigned int j = i * dim; j < (i + 1) * dim; j++) { sincos(input_a

[Bug sanitizer/94139] GCC9.2.0 build GCC8.2.0 break

2020-03-11 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94139 --- Comment #2 from 康 珊 --- This is a benchmark from phoronix (https://openbenchmarking.org/test/pts/build-gcc-1.1.2). The benchmark uses gcc-8.2.0.

[Bug sanitizer/94139] New: GCC9.2.0 build GCC8.2.0 break

2020-03-11 Thread kangshan0910 at hotmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: kangshan0910 at hotmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- Gcc8.2.0

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-09 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #33 from 康 珊 --- (In reply to Martin Liška from comment #32) > I can confirm it works for me with: > > diff --git a/common.gypi b/common.gypi > index 9502e92..3d8f04f 100644 > --- a/common.gypi > +++ b/common.gypi > @@ -195,8 +195,8

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-05 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #30 from 康 珊 --- (In reply to Martin Liška from comment #29) > > Thanks for your reminder. Currently I found there were 3 ways to solve the > > issue. > > 1.Remove “enable-lto” in configure and open “fno-strict-aliasing”. > > 2.Add

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-05 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #28 from 康 珊 --- (In reply to Martin Liška from comment #27) > (In reply to 康 珊 from comment #26) > > I found the previous build log is like "g++ -o > > /builddir/build/BUILD/node-v10.15.3/out/Release/cctest -pthread -rdynamic > >

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-05 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #26 from 康 珊 --- I found the previous build log is like "g++ -o /builddir/build/BUILD/node-v10.15.3/out/Release/cctest -pthread -rdynamic -m64

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-05 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #25 from 康 珊 --- OK. Then I will remove "enable-lto" in configure and try "-O3" with "-fno-strict-aliasing" to see whether it can solve the issue.

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-05 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #23 from 康 珊 --- (In reply to Martin Liška from comment #22) > (In reply to 康 珊 from comment #21) > > All of the experiments were did in according to the build steps I just gave > > to you. > > I'm sorry, but I would like to know

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-04 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #21 from 康 珊 --- All of the experiments were did in according to the build steps I just gave to you.

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-04 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #19 from 康 珊 --- I tried the following experiments: 1)Tried "__attribute__((noinline)) uv_unref(uv_handle_t*)", it could solve the issue. 2)Tried "__attribute__((noipa)) uv_unref(uv_handle_t*)", it could solve the issue. 2)Tried

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-04 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #18 from 康 珊 --- Sorry, actually I don't know the reason, and I failed to find any git comment for that configuration. It is involved from 10.14.2 build.

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-04 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #16 from 康 珊 --- OK. Our latest release nodejs package build steps are: export CFLAGS="$CFLAGS -O3 -falign-functions=32 -fno-math-errno -fno-semantic-interposition -fno-trapping-math " export CXXFLAGS="$CXXFLAGS -O3

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-04 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #14 from 康 珊 --- Yes, I built it with LDFLAGS="${LDFLAGS} -fno-lto". Moreover, I tried "__attribute__((noipa)) uv_unref(uv_handle_t*);" and it could solve the issue. So it may not be caused by the alias, right?

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-04 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #12 from 康 珊 --- Yes, I built it with LDFLAGS="${LDFLAGS} -fno-lto". Moreover, I tried "__attribute__((noipa)) uv_unref(uv_handle_t*);" and it could solve the issue. So it may not be caused by the alias, right?

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-03 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #10 from 康 珊 --- Hi Martin Liška, I tried to build it with "-O3 -fno-strict-aliasing -falign-functions=32 -fno-math-errno -fno-semantic-interposition -fno-trapping-math", but it still had the issue. Can "-fno-strict-aliasing" work

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-02 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #9 from 康 珊 --- That's great! Thank you very much for your support :)

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-04-01 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #7 from 康 珊 --- Thanks Martin Liška for your quick response. I'm sorry I'm not familiar with unique_ptr neither. Do you mean it is caused by the "Node" source logic itself?

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-03-30 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #2 from 康 珊 --- Created attachment 46062 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46062=edit octane benchmark part2

[Bug ipa/89893] Segmentation fault always occurs when node app is generated by gcc-8-branch@268745

2019-03-30 Thread kangshan0910 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893 --- Comment #1 from 康 珊 --- Created attachment 46061 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46061=edit octane benchmark part1