This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug regression/35671] GCC 4.4.x vs. 4.2.x performance regression
- From: "t dot artem at mailcity dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Aug 2009 14:14:33 -0000
- Subject: [Bug regression/35671] GCC 4.4.x vs. 4.2.x performance regression
- References: <bug-35671-5637@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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 consistently reproduced. The ideal testcase would be the smallest
> possible still showing the problem but anything below 100 lines of preprocessed
> code is probably small enough.
>
OK, let's be blunt.
99% of applications and libraries (that I use regularly) compiled with GCC >=
4.3 have bigger (binary code) sizes and lower speed. You can _easily_ check it
on your own. And I cannot come up with a really simple testcase because a new
compilation infrastructure introduced in GCC 4.3 made everything not so
brilliant.
The last but not the least - is that I'm not a developer at all, I have no
knowledge of assembler, thus I have no ability to analyze code produced by
different GCC versions. All I see is the end result and it's far from being
remarkable.
It seems like GCC developers are busy implementing new features forgetting
about the core mission of any compiler - creating the most efficient code for
all supported architectures. I'm closing this bug since I feel no one will step
up to even confirm it.
--
t dot artem at mailcity dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35671