[Bug regression/35671] GCC 4.4.x vs. 4.2.x performance regression

2009-07-07 Thread t dot artem at mailcity dot com
--- Comment #9 from t dot artem at mailcity dot com 2009-07-07 18:45 --- Qt 4.5.2 /lib directory (without *.debug files) occupies GCC 4.2.4: 43,649,379 bytes in 107 files GCC 4.4.0: 46,544,895 bytes in 107 files I don't like it at all. Compilation flags are still the same: -

[Bug regression/35671] GCC 4.4.x vs. 4.2.x performance regression

2009-08-08 Thread t dot artem at mailcity dot com
--- Comment #18 from t dot artem at mailcity dot com 2009-08-08 14:14 --- (In reply to comment #16) > > This is not a simple testcase. A simple testcase is a sufficiently small > self-contained compilable code that shows the problem in a way that can be > reliably and

[Bug target/26290] [4.1 Regression]: code pessimization wrt. GCC 4.0 probably due to TARGET_MEM_REF

2007-02-02 Thread t dot artem at mailcity dot com
--- Comment #16 from t dot artem at mailcity dot com 2007-02-02 17:02 --- Since GCC 4.1.2 RC1 is already out, does that mean that this bug is postponed till GCC 4.1.3/4.2.0? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26290

[Bug target/26290] [4.1/4.2 Regression]: code pessimization wrt. GCC 4.0 probably due to TARGET_MEM_REF

2008-03-09 Thread t dot artem at mailcity dot com
--- Comment #23 from t dot artem at mailcity dot com 2008-03-09 19:03 --- Since GCC 4.3.0 is out and this bug is no longer reproducible I suppose it's worth marking this bug as FIXED. Wow, it took exactly two years to fix this bug :-) -- t dot artem at mailcity dot com ch

[Bug regression/35671] New: [POSSIBLY NOT A BUG] GCC 4.3.0 vs. 4.2.3 observations

2008-03-22 Thread t dot artem at mailcity dot com
.0 vs. 4.2.3 observations Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: regression AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: t dot artem at mailcity dot com GCC

[Bug c++/35672] New: GCC 4.2.3 ICE on valid code: KDE 3.5.9 libdjvu compilation fails

2008-03-22 Thread t dot artem at mailcity dot com
gcc dot gnu dot org ReportedBy: t dot artem at mailcity dot com GCC host triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35672

[Bug c++/35672] GCC 4.2.3 ICE on valid code: KDE 3.5.9 libdjvu compilation fails

2008-03-22 Thread t dot artem at mailcity dot com
--- Comment #1 from t dot artem at mailcity dot com 2008-03-23 00:11 --- Created an attachment (id=15364) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15364&action=view) Compilation directory with .ii and .s output -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35672

[Bug c++/35672] GCC 4.2.3 ICE on valid code: KDE 3.5.9 libdjvu compilation fails

2008-03-22 Thread t dot artem at mailcity dot com
--- Comment #2 from t dot artem at mailcity dot com 2008-03-23 00:12 --- Sorry, a flag to blame is '-ftree-loop-linear' -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35672

[Bug regression/35671] [POSSIBLY NOT A BUG] GCC 4.3.0 vs. 4.2.3 observations

2008-03-24 Thread t dot artem at mailcity dot com
--- Comment #2 from t dot artem at mailcity dot com 2008-03-24 22:24 --- I'll check this out very soon - at least on Wine sources. Recompiling KDE isn't a task I'm very found of. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35671

[Bug regression/35671] [POSSIBLY NOT A BUG] GCC 4.3.0 vs. 4.2.3 observations

2008-03-24 Thread t dot artem at mailcity dot com
--- Comment #3 from t dot artem at mailcity dot com 2008-03-24 23:01 --- counting all .so and .a files in lib/wine directory: Without -ftree-vectorize: GCC 4.2.3: 46,884,566 bytes in 305 files GCC 4.3.0: 47,375,178 bytes in 305 files With -ftree-vectorize: GCC 4.2.3: 46,889,486

[Bug c/39741] New: [BUG or NOT?] Segmentation fault on valid code

2009-04-12 Thread t dot artem at mailcity dot com
dBy: t dot artem at mailcity dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39741

[Bug regression/35671] GCC 4.4.x vs. 4.2.x performance regression

2009-04-17 Thread t dot artem at mailcity dot com
--- Comment #4 from t dot artem at mailcity dot com 2009-04-18 01:44 --- Test configuration: Software: Linux kernel 2.6.28.9 x86, GCC 4.2.4, GCC 4.4.0 RC, http://www.rarlab.com/rar/unrarsrc-3.8.5.tar.gz Hardware: AMD64 Dual Core CPU 5600, 1MB x 2 level 2 cache RAM: DDR2 800MHz 4GB

[Bug regression/35671] GCC 4.4.x vs. 4.2.x performance regression

2009-04-18 Thread t dot artem at mailcity dot com
--- Comment #6 from t dot artem at mailcity dot com 2009-04-18 08:18 --- Many Linux distros compile binaries for a common lowest denominator so that you could run a distro on very old computers and CPUs - their developers in most cases choose -march=i686 or -march=i586. I compile

[Bug regression/35671] GCC 4.4.x vs. 4.2.x performance regression

2009-04-19 Thread t dot artem at mailcity dot com
--- Comment #8 from t dot artem at mailcity dot com 2009-04-19 13:51 --- If anyone cares to repeat my test results, here's a simple test case: 1) Obtain a large enough collection of WAV files (however I'm sure all other compressible material will also fit this test). If you

[Bug target/26290] [4.1 Regression]: code pessimization wrt. GCC 4.0 probably due to TARGET_MEM_REF

2007-05-18 Thread t dot artem at mailcity dot com
--- Comment #18 from t dot artem at mailcity dot com 2007-05-18 08:32 --- As for GCC 4.2.0 the bug is still relevant. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26290

[Bug rtl-optimization/40838] gcc shouldn't assume that the stack is aligned

2010-04-17 Thread t dot artem at mailcity dot com
--- Comment #67 from t dot artem at mailcity dot com 2010-04-17 14:28 --- Am I right assuming that GCC 4.5 is also affected by this bug? Is this bug going to be resolved? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40838

[Bug inline-asm/45160] New: [GCC 4.4.x regression] Invalid assembly code is generated for x86 architecture for faad2 library (AAC decode algorithm)

2010-08-01 Thread t dot artem at mailcity dot com
5 Status: UNCONFIRMED Severity: critical Priority: P3 Component: inline-asm AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: t dot artem at mailcity dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45160

[Bug inline-asm/45160] [GCC 4.4.x regression] Invalid assembly code is generated for x86 architecture for faad2 library (AAC decode algorithm)

2010-08-01 Thread t dot artem at mailcity dot com
--- Comment #1 from t dot artem at mailcity dot com 2010-08-02 00:09 --- faad2 2.7.0 exhibits the same misbehavior, you can download it here: http://downloads.sourceforge.net/faac/faad2-2.7.tar.bz2 No extra commands are required for compilation, just ./configure && make

[Bug inline-asm/45160] [GCC 4.4.x regression] Invalid assembly code is generated for x86 architecture for faad2 library (AAC decode algorithm)

2010-08-01 Thread t dot artem at mailcity dot com
--- Comment #2 from t dot artem at mailcity dot com 2010-08-02 00:31 --- Created an attachment (id=21368) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21368&action=view) faad2 2.7.0 complete sources with -save-temps Complete sources with -save-temps for GCC 4.2.4 and GC

[Bug inline-asm/45160] [4.4.x/4.5.x regression] Invalid assembly code is generated for x86 architecture for faad2 library (AAC decode algorithm)

2010-08-02 Thread t dot artem at mailcity dot com
--- Comment #3 from t dot artem at mailcity dot com 2010-08-02 13:09 --- I've just tested GCC 4.5.1 and it also miscompiles the source code. -- t dot artem at mailcity dot com changed: What|Removed |

[Bug inline-asm/45160] [4.4.x/4.5.x regression] Invalid assembly code is generated for x86 architecture for faad2 library (AAC decode algorithm)

2010-08-02 Thread t dot artem at mailcity dot com
--- Comment #4 from t dot artem at mailcity dot com 2010-08-02 13:10 --- Created an attachment (id=21369) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21369&action=view) faad2 2.7.0 complete sources with -save-temps for GCC 4.5.1 -- http://gcc.gnu.org/bugzilla/show_

[Bug inline-asm/45160] [4.4.x/4.5.x regression] Invalid assembly code is generated for x86 architecture for faad2 library (AAC decode algorithm)

2010-08-02 Thread t dot artem at mailcity dot com
--- Comment #5 from t dot artem at mailcity dot com 2010-08-02 13:15 --- I've found the culprit (or better say mplayer developer hinted), it is -fstrict-aliasing optimization. With -fno-strict-aliasing GCC 4.4.x and 4.5.x produce proper code. Please, advise. --

[Bug inline-asm/45160] [4.4.x/4.5.x regression] Invalid assembly code is generated for x86 architecture for faad2 library (AAC decode algorithm)

2010-08-02 Thread t dot artem at mailcity dot com
--- Comment #7 from t dot artem at mailcity dot com 2010-08-02 15:49 --- (In reply to comment #6) > Why CC me? I have no clue about faad2, the strict-aliasing thing hints > at errors in faad2, not gcc. > Richard, I don't know who is who amongst GCC developers,

[Bug inline-asm/45160] [4.4.x/4.5.x regression] Invalid assembly code is generated for x86 architecture for faad2 library (AAC decode algorithm)

2010-08-02 Thread t dot artem at mailcity dot com
--- Comment #9 from t dot artem at mailcity dot com 2010-08-02 20:27 --- The culprit is the ic_predict.c file. When I compile it with -fno-strict-aliasing (while everything else is being compiled with -fstrict-aliasing) libfaad works correctly. These are the warnings which I get from

[Bug c/45312] New: GCC 4.4.4 miscompiles (?) the Linux kernel, makes kernel unusable

2010-08-17 Thread t dot artem at mailcity dot com
, makes kernel unusable Product: gcc Version: 4.4.4 Status: UNCONFIRMED Severity: blocker Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: t dot artem at mailcity dot

[Bug c/45312] GCC 4.4.4 miscompiles (?) the Linux kernel, makes kernel unusable

2010-08-17 Thread t dot artem at mailcity dot com
--- Comment #3 from t dot artem at mailcity dot com 2010-08-18 04:05 --- OK, then I'm closing this bug report, since I don't have enough experience to actually find a file that is being miscompiled. (And according to Linus it can be any out of dozens). -- t dot artem a

[Bug middle-end/45312] GCC 4.4.4 miscompiles (?) the Linux kernel, makes kernel unusable

2010-08-17 Thread t dot artem at mailcity dot com
--- Comment #5 from t dot artem at mailcity dot com 2010-08-18 05:11 --- This crash occurs upon loading modules, so it's *very* difficult to trace/pinpoint it. Most likely no kernel options have any effect on it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45312

[Bug middle-end/45312] GCC 4.4.4 miscompiles (?) the Linux kernel, makes kernel unusable

2010-08-18 Thread t dot artem at mailcity dot com
--- Comment #7 from t dot artem at mailcity dot com 2010-08-18 20:00 --- I bet this bug can be triggered in a VM (e.g. in VirtualBox) too, so I'll try to debug it later. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45312

[Bug inline-asm/45160] [4.4.x/4.5.x regression] Invalid assembly code is generated for x86 architecture for faad2 library (AAC decode algorithm)

2010-09-06 Thread t dot artem at mailcity dot com
--- Comment #11 from t dot artem at mailcity dot com 2010-09-06 20:19 --- (In reply to comment #9) > Maybe GCC developers could devise a patch for this file because > http://www.audiocoding.com/faad2.html site seems to be dead. > (In reply to comment #10) > Not a gcc b

[Bug rtl-optimization/40838] gcc shouldn't assume that the stack is aligned

2010-04-28 Thread t dot artem at mailcity dot com
--- Comment #69 from t dot artem at mailcity dot com 2010-04-29 02:12 --- (In reply to comment #64) > Subject: Bug 40838 > This patch is not sufficient, some applications still crash after I've applied it to GCC 4.4 branch (to be more precise gcc-4.4-20100427.tar.bz2

[Bug rtl-optimization/40838] gcc shouldn't assume that the stack is aligned

2010-04-29 Thread t dot artem at mailcity dot com
--- Comment #71 from t dot artem at mailcity dot com 2010-04-29 07:24 --- (In reply to comment #70) No, I haven't used -mstackrealign as I presumed that the patch is sufficient - and since you make me sound like I'm wrong, then the patch is also wrong, since GCC must be p

[Bug rtl-optimization/40838] gcc shouldn't assume that the stack is aligned

2010-04-29 Thread t dot artem at mailcity dot com
--- Comment #74 from t dot artem at mailcity dot com 2010-04-29 08:29 --- Guys, you are talking in riddles. There's a fact: with -msse2 -O2 -m32 flags GCC generate bad code for some properly coded applications, so I wonder what users are supposed to do. There are alread

[Bug target/26290] [4.1/4.2 Regression]: code pessimization wrt. GCC 4.0 probably due to TARGET_MEM_REF

2007-11-04 Thread t dot artem at mailcity dot com
--- Comment #21 from t dot artem at mailcity dot com 2007-11-04 13:42 --- > I would say let's close this as fixed. Do you mean that GCC 4.1 and 4.2 will never have this bug fixed and we have to wait till 4.3 is out? Besides, have you tested this bug on architectures other th

[Bug regression/26290] New: [4.1 Regression]: some loop optimizations no longer run at -O2

2006-02-14 Thread t dot artem at mailcity dot com
Priority: P3 Component: regression AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: t dot artem at mailcity dot com GCC build triplet: i686-pc-linux-gnu-gcc GCC host triplet: i686-pc-linux-gnu-gcc GCC target triplet: i686-pc-linux-gnu-gcc http://gcc.gnu.org/bugzilla

[Bug regression/26290] [4.1 Regression]: some loop optimizations no longer run at -O2

2006-02-14 Thread t dot artem at mailcity dot com
--- Comment #1 from t dot artem at mailcity dot com 2006-02-14 18:52 --- Created an attachment (id=10850) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10850&action=view) A testcase Here's a testcase. For those who couldn't understand the point: GCC 4.1.0 -O2

[Bug target/26290] [4.1 Regression]: some loop optimizations no longer run at -O2

2006-02-17 Thread t dot artem at mailcity dot com
-- t dot artem at mailcity dot com changed: What|Removed |Added Severity|minor |major http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26290

[Bug target/26290] [4.1 Regression]: code pessimization wrt. GCC 4.0 probably due to TARGET_MEM_REF

2006-02-20 Thread t dot artem at mailcity dot com
--- Comment #12 from t dot artem at mailcity dot com 2006-02-21 04:56 --- This bug may affect real applications performance so I believe it's worth being resolved for 4.1.0 release. What if one changes severity to critical though certanly this bug isn't critical?