Hi Joseph,
I hit the following problem when trying to build a ppc64 Linux kernel
from svn today:
# gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wmissing-prototypes
-Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep
scripts/basic/fixdep.c
cc1: error: unrecognized command line o
On Aug 12 2010, Steve Kargl wrote:
Your observation re-enforces the notion that doing
benchmarks properly is difficult. I forgot about
the lapack inquiry routines. One would think that
some 20+ year after F90, that Dongarra and colleagues
would use the intrinsic numeric inquiry functions.
Al
On Fri, 13 Aug 2010, Anton Blanchard wrote:
> Hi Joseph,
>
> I hit the following problem when trying to build a ppc64 Linux kernel
> from svn today:
>
> # gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wmissing-prototypes
> -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep
> scr
> > I hit the following problem when trying to build a ppc64 Linux kernel
> > from svn today:
> >
> > # gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wmissing-prototypes
> > -Wstrict-prototypes -O2 -fomit-frame-pointer -o
> > scripts/basic/fixdep scripts/basic/fixdep.c
>
> The options passed to inte
On Fri, 13 Aug 2010, Arnaud Charlet wrote:
> > The options passed to internal binaries such as cc1 are not a documented
> > public interface to GCC, so if you pass such options via -Wp you must
> > expect to need to change your makefiles when the GCC-internal interfaces
> > change. Instead, you s
> Allowing the same option to behave differently in the driver and in cc1
> regarding whether it takes operands seems like error-prone complexity;
> every piece of code that now or in the future looks at CL_SEPARATE will
> need also to check whether it is in the driver or in cc1. Why is this
> cod
On Mon, May 17, 2010 at 10:44:57AM +0400, Maxim Kuvyrkov wrote:
> CodeSourcery is working on improving performance for Intel's Core 2 and
> Core i7 families of processors.
>
> CodeSourcery plans to add support for unaligned vector instructions, to
> provide fine-tuned scheduling support and to
Ralf W. Grosse-Kunstleve wrote:
Without knowing the compiler options, the results of any benchmark
are meaningless.
I used
gfortran -o dsyev_test_gfortran -O3 -ffast-math dsyev_test.f
If you work on a 32bit x86 system, you really should use -march=native
and possibly -mfpmath=sse - otherw
hello,
I seem to be stuck with this error(below) when building nss
../dist/public/dbm pkix_pl_ldaptemplates.c
{standard input}: Assembler messages:
{standard input}:954: Error: junk at end of line, first unrecognized
character is `6'
{standard input}:954: Error: junk at end of line, first unrecog
On Sat, Aug 14, 2010 at 12:08:21AM +0200, Tobias Burnus wrote:
>
> In terms of options, I think -funroll-loops should also be used as it
> usually improves performance (it is not enabled by any -O... option).
>
I wonder if gfortran should check if -O and -O2 is given,
and then add -funroll-loop
Justin Mattock writes:
> I seem to be stuck with this error(below) when building nss
>
> ../dist/public/dbm pkix_pl_ldaptemplates.c
> {standard input}: Assembler messages:
> {standard input}:954: Error: junk at end of line, first unrecognized
> character is `6'
> {standard input}:954: Error: jun
11 matches
Mail list logo
