http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56309
--- Comment #21 from Igor Zamyatin 2013-02-15
06:49:53 UTC ---
(In reply to comment #18)
> Following patch is a big hammer approach to the problem, intended only for
> benchmarking
>
> --cut here--
> Index: common/config/i386/i386-comm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56511
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56511
--- Comment #4 from Igor Zamyatin 2013-03-07
08:52:53 UTC ---
Doesn't first argument of memcpy which is called from memcpy_vec have unknown
(1byte) alignment? If yes, how PPC managed to produce vector instructions?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55362
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56676
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56680
Bug #: 56680
Summary: ICE for spec2K's 178.galgel and 200.sixtrack for
x86_64 at O3
Classification: Unclassified
Product: gcc
Version: 4.9.0
Status: UNCONFI
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34949
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56885
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56885
Igor Zamyatin changed:
What|Removed |Added
CC||ysrumyan at gmail dot com
--- C
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57084
Bug #: 57084
Summary: 483. xalancbmk run fails with -O2 -flto for i686
Classification: Unclassified
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57124
Bug #: 57124
Summary: 254.gap@spec2000 got miscompare after r198413
Classification: Unclassified
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57124
--- Comment #5 from Igor Zamyatin ---
Indeed, -fwrapv helps to run 254.gap successfully
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54095
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53942
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54200
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54200
--- Comment #11 from Igor Zamyatin 2012-08-13
12:46:48 UTC ---
Right! Sorry for the noise...
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53671
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53671
--- Comment #14 from Igor Zamyatin 2012-08-22
11:24:17 UTC ---
Thanks!
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54390
Bug #: 54390
Summary: [AVX] FAIL: gcc.dg/vect/no-tree-sra-bb-slp-pr50730.c
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50557
--- Comment #16 from Igor Zamyatin 2012-10-04
11:17:00 UTC ---
Seems with LRA code is fast again
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54889
Bug #: 54889
Summary: [4.8 Regression] Revision 191983 gives compfail for
465.tonto in SPEC CPU 2006 when use -O3 -mavx
Classification: Unclassified
Product: gcc
Version: 4.8.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54889
--- Comment #2 from Igor Zamyatin 2012-10-11
11:40:39 UTC ---
Now I see no compfails on the whole spec test 465
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54889
--- Comment #3 from Igor Zamyatin 2012-10-16
11:12:47 UTC ---
Jakub, are you going to commit the fix or there are some issues with it?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54942
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54944
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54942
--- Comment #4 from Igor Zamyatin 2012-10-23
08:52:30 UTC ---
Does it still happen? I don't see oom now for my test
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54472
--- Comment #6 from Igor Zamyatin 2012-10-24
11:09:49 UTC ---
Have you managed to check the patch?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55104
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55006
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54985
--- Comment #11 from Igor Zamyatin 2012-10-30
08:32:01 UTC ---
Are there any plans to backport this to 4.7?
: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: izamyatin at gmail dot com
CC: mjambor at suse dot cz
Target: x86
Happens due to r198821.
Fail:
lto1: internal compiler error: in propagate_controlled_uses, at ipa-prop.c:2552
0x71753f
-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: izamyatin at gmail dot com
CC: eraman at google dot com
Target: x86
gfortran -c -o mp2ddi.fppized.o -O2 -ffast-math -ffixed-form mp2ddi.fppized.f
mp2ddi.fppized.f: In function 'pm
-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: izamyatin at gmail dot com
CC: rguenther at suse dot de
Target: x86
Output:
gcc -c -o perl.o -DSPEC_CPU2000_LP64 -DSPEC_CPU2000_LINUX_I386
-DSPEC_CPU2000_NEED_BOOL -DSPEC_CPU2000_GLIBC22
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57393
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57337
--- Comment #4 from Igor Zamyatin ---
For the record - 191.fma3d from spec2K fails with similar error
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: izamyatin at gmail dot com
CC: vmakarov at redhat dot com
Target: x86_64
Happens only on x86_64 with just "-O2 -ffast-math" flags:
co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57208
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: izamyatin at gmail dot com
CC: jh at suse dot cz
Target: x86
Note that before r198917 there was compilation fail for this test.
Compile flags: -O3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57468
--- Comment #3 from Igor Zamyatin ---
Patch is here http://gcc.gnu.org/ml/gcc-patches/2013-06/msg00357.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57468
--- Comment #4 from Igor Zamyatin ---
So following commit fixed the issue
commit 3620f4de1b49b0bfffe5f812b2d259e5c72c5c61
Author: vmakarov
Date: Thu Jun 6 21:12:06 2013 +
2013-06-06 Vladimir Makarov
PR rtl-optimization/574
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: izamyatin at gmail dot com
CC: jh at suse dot cz
Target: i686
For instance, 164.gzip has Segmentation fault. (tried on trunk, revision
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57602
--- Comment #2 from Igor Zamyatin ---
For both cases we have calls of static routines where address of some static
variable is being passed.
Since all this could be seen only for 32 bits, problem looks like some
attribute which allows the routine
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57602
Igor Zamyatin changed:
What|Removed |Added
CC||hubicka at ucw dot cz
--- Comment #3 from
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57602
--- Comment #4 from Igor Zamyatin ---
Created attachment 30377
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30377&action=edit
Untested patch that corrects the cleanup
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57602
--- Comment #6 from Igor Zamyatin ---
Jan, have you had a chance to look at the problem?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57879
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58298
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50176
Bug #: 50176
Summary: [4.6/4.7 Regression] 4.7 generates spill-fill dealing
with char->int conversion
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50176
--- Comment #2 from Igor Zamyatin 2011-08-25
13:17:36 UTC ---
For gcc with
Target: x86_64-unknown-linux-gnu
Configured with: ../configure --disable-bootstrap --enable-languages=c,c++
--prefix=/export/users/izamyati/gcc_4_6_2_prefix/
Thread model
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50176
--- Comment #5 from Igor Zamyatin 2011-08-29
11:48:12 UTC ---
Yes, looks like this revision is the reason
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50176
--- Comment #7 from Igor Zamyatin 2011-09-14
14:30:35 UTC ---
In RTL everythin is vice-versa, additional instruction appears:
For the "bad" case couple instructions are responsible for cb load (asmcons
dump):
(insn 52 51 53 5 (set (reg:QI 83 [
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50176
Igor Zamyatin changed:
What|Removed |Added
CC||vmakarov at redhat dot com
--- Comment #8
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50557
Bug #: 50557
Summary: [4.7 Regression] Register pressure increase after
reassociation (x86, 32 bits)
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50557
--- Comment #1 from Igor Zamyatin 2011-09-28
11:52:18 UTC ---
Created attachment 25373
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25373
testcase
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50557
--- Comment #3 from Igor Zamyatin 2011-09-29
08:34:45 UTC ---
William, thanks for quick response!
With -funroll-loops regression is still present.
Do you want me to attach some dumps?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50557
--- Comment #6 from Igor Zamyatin 2011-10-07
10:33:33 UTC ---
Indeed, overall register pressure is not increased. Even before IRA dumps show
that register pressure is actually kept on the same level.
Looks like it is a tricky case we met.
Firs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50164
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50898
Bug #: 50898
Summary: Register allocation depends on function return
expression on x86 32-bits
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONF
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50962
Bug #: 50962
Summary: Additional opportunity for AGU stall avoidance
optimization for Atom processor
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50962
--- Comment #1 from Igor Zamyatin 2011-11-02
12:00:55 UTC ---
Created attachment 25688
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25688
testcase
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53128
--- Comment #4 from Igor Zamyatin 2012-05-03
11:09:15 UTC ---
Isn't it too aggressive from user perspective to perform such transformation
even without warning? Especially for the case when that "wrong" read is not
used later.
Sure it is dangerou
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53128
--- Comment #6 from Igor Zamyatin 2012-05-04
13:19:07 UTC ---
Compiler does not simply see such code, it happens after some analysis, right?
For example, after work of infer_loop_bounds_from_undefined which makes some
assumptions and I believe ca
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53209
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53161
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53161
--- Comment #7 from Igor Zamyatin 2012-05-11
10:07:07 UTC ---
Error message for x86 compilation
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53437
Bug #: 53437
Summary: FAIL: gcc.dg/guality/inline-params.c -O0
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53555
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53588
Bug #: 53588
Summary: [4.8 Regression] FAIL: gfortran.dg/vect/pr32380.f
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53081
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53081
--- Comment #16 from Igor Zamyatin 2012-06-20
08:44:44 UTC ---
Also cause of http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53726
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53750
Bug #: 53750
Summary: x86 bootstrap failure since 188876
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53750
--- Comment #1 from Igor Zamyatin 2012-06-22
10:14:40 UTC ---
Oh, I see that fix was already checked in. Great!
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53787
Bug #: 53787
Summary: Possible lto improvement
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53787
--- Comment #2 from Igor Zamyatin 2012-06-27
17:56:48 UTC ---
The testcase was reduced from some real app. No inlining happened there.
Do you think this testcase is bad?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53787
--- Comment #4 from Igor Zamyatin 2012-06-28
08:17:13 UTC ---
Created attachment 27714
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27714
gfort assembler
"Init" routine should be inspected here
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53787
--- Comment #5 from Igor Zamyatin 2012-06-28
08:22:11 UTC ---
Created attachment 27715
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27715
ifort assembler
"Init" routine looks much better here
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53787
--- Comment #7 from Igor Zamyatin 2012-07-19
19:09:49 UTC ---
Any thoughts here?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54084
Bug #: 54084
Summary: Bunch of fails for x86
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54084
--- Comment #3 from Igor Zamyatin 2012-07-24
17:16:11 UTC ---
Seems ok now
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54084
--- Comment #5 from Igor Zamyatin 2012-07-26
08:44:01 UTC ---
Looks like r189812 fixed some failures but not all of them.
Patch from comment 2 fixes all problems
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54156
--- Comment #2 from Igor Zamyatin 2012-08-01
15:57:42 UTC ---
Author: wschmidt
Date: Tue Jul 31 12:25:04 2012 +
gcc:
2012-07-31 Bill Schmidt
PR tree-optimization/53773
* tree-vectorizer.h (struct _loop_vec_inf
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54156
--- Comment #3 from Igor Zamyatin 2012-08-03
13:38:05 UTC ---
There are 6 "* 10" in a dump for AVX (additional 2 occur when vectorizer
consider 32-byte vectorization)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54156
--- Comment #7 from Igor Zamyatin 2012-08-03
19:24:40 UTC ---
There are no those fails now, thanks! The bug could be closed.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52241
--- Comment #1 from Igor Zamyatin 2012-02-15
09:06:49 UTC ---
BTW, this is a 4.7 regression
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52241
--- Comment #16 from Igor Zamyatin 2012-02-19
18:58:41 UTC ---
Jakub, could you please clarify your statement - "But libstdc++.so.6's tree.cc
has been compiled with
-fPIC -DPIC before Benjamin's change and is compiled with those flags after
those
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52395
Bug #: 52395
Summary: [4.7 Regression] Alignment issue at O2
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52395
--- Comment #2 from Igor Zamyatin 2012-02-27
09:47:38 UTC ---
Right, more conservative :)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52395
--- Comment #3 from Igor Zamyatin 2012-02-27
09:49:38 UTC ---
x86_64 indeed, sorry
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52563
Bug #: 52563
Summary: FAIL: gcc.dg/tree-ssa/scev-[3,4].c
scan-tree-dump-times optimized "&a" 1
Classification: Unclassified
Product: gcc
Version: tree-ssa
Status: UNC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52406
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52626
Bug #: 52626
Summary: make check fixinclude test FAILURES
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52632
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52272
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52272
--- Comment #10 from Igor Zamyatin 2012-03-29
11:04:27 UTC ---
Is it possible to look at the regressed test-case and gcc dumps with
-fdump-tree-ivopts-details option w/o that change?
Thanks in advance
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52865
Bug #: 52865
Summary: GCC can't vectorize fortran loop but able to vectorize
similar c-loop
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRM
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52865
--- Comment #1 from Igor Zamyatin 2012-04-04
13:27:11 UTC ---
Created attachment 27088
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27088
C test
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52865
--- Comment #5 from Igor Zamyatin 2012-04-04
15:20:41 UTC ---
Seems it doesn't like non-empty latch block in Fortran case
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52868
Bug #: 52868
Summary: [4.6/4.7/4.8 Regression] 4.6 is faster on Atom
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Pri
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52916
--- Comment #5 from Igor Zamyatin 2012-04-12
13:55:54 UTC ---
With this patch 481.wrf is ok
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52865
--- Comment #6 from Igor Zamyatin 2012-04-16
07:16:56 UTC ---
Any ideas what exactly does prevent the vectorization in the case of Fortran?
1 - 100 of 236 matches
Mail list logo