This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: A user's experiences with GCC-3.4 snapshots


On Wed, Sep 17, 2003 at 09:01:17AM +0200, Steven Bosscher wrote:
> Op di 16-09-2003, om 21:57 schreef Art Haas:
> > I've seen more memory usage with both C and C++ code, though I don't
> > recall seeing anything as dramatic as that. The compiler is a little
> > slower that GCC-3.3 also, but that is an issue brought up by many people
> > over and over again, and I know the developers here enough about that.
> 
> Can you tell us how you configured GCC 3.4?  In my experience it is
> almost always faster than 3.3 -- maybe you had checking enabled or
> something like that???
> 

I use this script to configure my builds ...

#!/bin/sh

params='finline-limit=50000'
CPPFLAGS="-DNDEBUG" CFLAGS="-O2 -march=pentium-mmx -std=gnu99 ${params}" \
CXXFLAGS="-O2 -march=pentium-mmx ${params}" \
/usr/src/gcc_3_4_branch/gcc/configure \
--prefix=/opt/gnu --enable-shared \
--enable-__cxa_atexit --enable-languages="c,c++,f77,objc" \
--disable-checking

> > The parrot example seems to me to be a good example of a C file that 
> > displays a dramatic slowdown for a particular code construction, and 
> > makes a good testcase for testing computed goto functionality in the
> > compiler.
> 
> If there's no bug report for this, please file one (with test case ;-). 
> We can't have such slowdowns...
> 

I'll file a bug report today.

Art
-- 
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.

-Thomas Jefferson to James Smith, 1822


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]