oprofile configure?

oprofile configure?

[Azer, William]

[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]

Hi,

i have natively built oprofile for sb1 platform and i get a lot of warnings from the compiler.  i had to use --disable-werror in order to build.  has anyone encountered this?  am i doing something wrong?

i did compile, install and run.

thx,

Bill Azer


if g++ -DHAVE_CONFIG_H -I. -I. -I..  -I ../libutil -I ../libop  -W -Wall -fno-common -ftemplate-depth-50 -g -O2 -MT op_exception.o -MD -MP -MF ".deps/op_exception.Tpo" -c -o op_exception.o op_exception.cpp; \
then mv -f ".deps/op_exception.Tpo" ".deps/op_exception.Po"; else rm -f ".deps/op_exception.Tpo"; exit 1; fi
/usr/lib32/gcc/mips64-montavista-linux/3.4.3/../../../../include/c++/3.4.3/bits/basic_string.h: In static member function `static std::basic_string<_CharT, _Traits, _Alloc>::_Rep& std::basic_string<_CharT, _Traits, _Alloc>::_Rep::_S_empty_rep() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]':
/usr/lib32/gcc/mips64-montavista-linux/3.4.3/../../../../include/c++/3.4.3/bits/basic_string.h:215:   instantiated from `void std::basic_string<_CharT, _Traits, _Alloc>::_Rep::_M_dispose(const _Alloc&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]'
/usr/lib32/gcc/mips64-montavista-linux/3.4.3/../../../../include/c++/3.4.3/bits/basic_string.h:418:   instantiated from `std::basic_string<_CharT, _Traits, _Alloc>::~basic_string() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]'
op_exception.cpp:21:   instantiated from here
/usr/lib32/gcc/mips64-montavista-linux/3.4.3/../../../../include/c++/3.4.3/bits/basic_string.h:178: warning: dereferencing type-punned pointer will break strict-aliasing rules

[-- Attachment #2: Type: text/html, Size: 2306 bytes --]

oprofile configure?

[Azer, William]

[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]

Hi,

i have natively built oprofile for sb1 platform and i get a lot of warnings from the compiler.  i had to use --disable-werror in order to build.  has anyone encountered this?  am i doing something wrong?

i did compile, install and run.

thx,

Bill Azer


if g++ -DHAVE_CONFIG_H -I. -I. -I..  -I ../libutil -I ../libop  -W -Wall -fno-common -ftemplate-depth-50 -g -O2 -MT op_exception.o -MD -MP -MF ".deps/op_exception.Tpo" -c -o op_exception.o op_exception.cpp; \
then mv -f ".deps/op_exception.Tpo" ".deps/op_exception.Po"; else rm -f ".deps/op_exception.Tpo"; exit 1; fi
/usr/lib32/gcc/mips64-montavista-linux/3.4.3/../../../../include/c++/3.4.3/bits/basic_string.h: In static member function `static std::basic_string<_CharT, _Traits, _Alloc>::_Rep& std::basic_string<_CharT, _Traits, _Alloc>::_Rep::_S_empty_rep() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]':
/usr/lib32/gcc/mips64-montavista-linux/3.4.3/../../../../include/c++/3.4.3/bits/basic_string.h:215:   instantiated from `void std::basic_string<_CharT, _Traits, _Alloc>::_Rep::_M_dispose(const _Alloc&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]'
/usr/lib32/gcc/mips64-montavista-linux/3.4.3/../../../../include/c++/3.4.3/bits/basic_string.h:418:   instantiated from `std::basic_string<_CharT, _Traits, _Alloc>::~basic_string() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]'
op_exception.cpp:21:   instantiated from here
/usr/lib32/gcc/mips64-montavista-linux/3.4.3/../../../../include/c++/3.4.3/bits/basic_string.h:178: warning: dereferencing type-punned pointer will break strict-aliasing rules

[-- Attachment #2: Type: text/html, Size: 2306 bytes --]

Re: oprofile configure?

[Jim Wilson]

On Tue, 2006-09-26 at 10:34 -0400, Azer, William wrote:
> i have natively built oprofile for sb1 platform and i get a lot of
> warnings from the compiler.  i had to use --disable-werror in order to
> build.  has anyone encountered this?  am i doing something wrong?

You didn't mention the oprofile version, the gcc version, or the kernel
version, which are the important bits here.  I can see from the error
messages that you have gcc-3.4.3, and a montavista kernel.
> 
I tried oprofile-0.9.2.  I was unable to get -Werror used in the
compiler.  Looking at the configure script, I see that -Werror is
disabled unless you have a snapshot from the cvs tree.  Not even
--enable-werror can turn it on.  I'm guessing that you are using the cvs
tree.

This looks like a bug in the gcc that you are using.  I can't reproduce
it on other systems, but I can reproduce it on a similar MontaVista
system.  I can't reproduce it with later FSF gcc releases on the same
MontaVista system.  It isn't immediately obvious what changed to fix
this.
-- 
Jim Wilson, GNU Tools Support, http://www.specifix.com

RE: oprofile configure?

[Azer, William]

[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]

Yes, i was using oprofile 0.9.2cvs.  I can provide the code.  The -Werror is enabled by default.

i have also been having trouble running it with trying to debug a executable program.  i used the opcontrol to tell it the image,start,dump,stop  then i used opreport -l <image>.  i couldn't get the sample data.  i tried opannotate and that didn't work either.

i have had better luck with gprof.

# Define the identity of the package.
 PACKAGE=oprofile
 VERSION=0.9.2cvs

i am using 2.6.17.7 from linux-mips.org with gcc 3.4.3


thx,

Bill Azer

-----Original Message-----
From: Jim Wilson [mailto:wilson@specifix.com]
Sent: Wed 9/27/2006 5:49 PM
To: Azer, William
Cc: linux-mips@linux-mips.org
Subject: Re: oprofile configure?
 
On Tue, 2006-09-26 at 10:34 -0400, Azer, William wrote:
> i have natively built oprofile for sb1 platform and i get a lot of
> warnings from the compiler.  i had to use --disable-werror in order to
> build.  has anyone encountered this?  am i doing something wrong?

You didn't mention the oprofile version, the gcc version, or the kernel
version, which are the important bits here.  I can see from the error
messages that you have gcc-3.4.3, and a montavista kernel.
> 
I tried oprofile-0.9.2.  I was unable to get -Werror used in the
compiler.  Looking at the configure script, I see that -Werror is
disabled unless you have a snapshot from the cvs tree.  Not even
--enable-werror can turn it on.  I'm guessing that you are using the cvs
tree.

This looks like a bug in the gcc that you are using.  I can't reproduce
it on other systems, but I can reproduce it on a similar MontaVista
system.  I can't reproduce it with later FSF gcc releases on the same
MontaVista system.  It isn't immediately obvious what changed to fix
this.
-- 
Jim Wilson, GNU Tools Support, http://www.specifix.com



[-- Attachment #2: Type: text/html, Size: 2617 bytes --]

RE: oprofile configure?

[Azer, William]

[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]

Yes, i was using oprofile 0.9.2cvs.  I can provide the code.  The -Werror is enabled by default.

i have also been having trouble running it with trying to debug a executable program.  i used the opcontrol to tell it the image,start,dump,stop  then i used opreport -l <image>.  i couldn't get the sample data.  i tried opannotate and that didn't work either.

i have had better luck with gprof.

# Define the identity of the package.
 PACKAGE=oprofile
 VERSION=0.9.2cvs

i am using 2.6.17.7 from linux-mips.org with gcc 3.4.3


thx,

Bill Azer

-----Original Message-----
From: Jim Wilson [mailto:wilson@specifix.com]
Sent: Wed 9/27/2006 5:49 PM
To: Azer, William
Cc: linux-mips@linux-mips.org
Subject: Re: oprofile configure?
 
On Tue, 2006-09-26 at 10:34 -0400, Azer, William wrote:
> i have natively built oprofile for sb1 platform and i get a lot of
> warnings from the compiler.  i had to use --disable-werror in order to
> build.  has anyone encountered this?  am i doing something wrong?

You didn't mention the oprofile version, the gcc version, or the kernel
version, which are the important bits here.  I can see from the error
messages that you have gcc-3.4.3, and a montavista kernel.
> 
I tried oprofile-0.9.2.  I was unable to get -Werror used in the
compiler.  Looking at the configure script, I see that -Werror is
disabled unless you have a snapshot from the cvs tree.  Not even
--enable-werror can turn it on.  I'm guessing that you are using the cvs
tree.

This looks like a bug in the gcc that you are using.  I can't reproduce
it on other systems, but I can reproduce it on a similar MontaVista
system.  I can't reproduce it with later FSF gcc releases on the same
MontaVista system.  It isn't immediately obvious what changed to fix
this.
-- 
Jim Wilson, GNU Tools Support, http://www.specifix.com



[-- Attachment #2: Type: text/html, Size: 2617 bytes --]

RE: oprofile configure?

[Jim Wilson]

On Wed, 2006-09-27 at 18:05 -0400, Azer, William wrote:
> i have also been having trouble running it with trying to debug a
> executable program.

oprofile not working is probably not a gcc problem, and hence probably
outside my area of expertise.  I don't have much experience with
oprofile.  I was just looking at the gcc issue that you noticed.
-- 
Jim Wilson, GNU Tools Support, http://www.specifix.com

Re: oprofile configure?

[Ralf Baechle]

On Tue, Sep 26, 2006 at 10:34:12AM -0400, Azer, William wrote:

> i have natively built oprofile for sb1 platform and i get a lot of warnings from the compiler.  i had to use --disable-werror in order to build.  has anyone encountered this?  am i doing something wrong?

For a long time there has been no release of oprofile so only versions from
CVS did work on MIPS:  However there has been a release of 0.9.2 on
September 15 which so I hope is the first release of oprofile that will
work out of the box for MIPS.

I believe -Werror is a remarkably bad idea for any software release no
matter how beneficial it may be during development ...

  Ralf