> We're already on it.  "-pedantic" gets used by default in debug mode
> on gcc, and gets tested regularly on gcc 4.5, irregularly on gcc 4.6
> and others.

Ah, great.

> We don't:
>
> roystgnr@mycroft:~/libmesh/svn$ METHOD=dbg make echo | grep O2
> roystgnr@mycroft:~/libmesh/svn$

That's odd to me. Where do the flags come from?

> Because we default to METHOD=opt.  No doubt if we defaulted to
> METHOD=dbg then we'd get complaints like "why does METHOD=opt even
> need to be provided?"

Sorry to not be clear, that's not what I meant.

> I find "./configure && make && METHOD=dbg make" fairly convenient,

This is what I meant. "./configure --enable-debug && make" vs.
"./configure --disable-debug && make" much like every other package
I've dealt with.

> but
> there may be some bug with clang that's not getting triggered with
> icc, gcc, or even the Portland Group stuff I've used lately.  If
> clang does need its own special snowflake options too I'd like to
> figure out what they are so we can add a entry to m4/compiler.m4
> accordingly.

I would like to know as well but currently have no idea.

> Four O2 C/CXXFLAGS sets sounds right; one for each of devel, prof,
> oprof, and opt modes.  Are any of those on dbg mode for you?

Yes, sorry, that was not the complete output. I have -O2 in the dbg
section of Make.common as well.

> roystgnr@mycroft:~/libmesh/svn$ METHOD=dbg make echo | grep
> --after-context=1 'C.*FLAGS'
> libmesh_CPPFLAGS:
> -DDEBUG  -DPETSC_USE_DYNAMIC_LIBRARIES
> --
> libmesh_CFLAGS:
> -g -Wimplicit -fPIC --
> libmesh_CXXFLAGS:
> -O0 -felide-constructors -g -ansi -pedantic -W -Wall -Wextra -Wno-long-long
> -Wunused -Wpointer-arith -Wformat -Wparentheses -fPIC -Woverloaded-virtual
> -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC

$ METHOD=dbg make echo | grep --after-context=1 'C.*FLAGS'
libmesh_CPPFLAGS:
-DDEBUG  -DPETSC_USE_DYNAMIC_LIBRARIES
--
libmesh_CFLAGS:
-g -O2
--
libmesh_CXXFLAGS:
-g -O2

> Ah - I didn't realize you'd told it to spit out the internal lines as
> well.

It's nothing that I manually set, just what the stack trace spit out.

> What's the command line option set look like?  Is -O2 in the output
> you see with "METHOD=dbg make -n"?

Yes (though too much output to copy and paste)

> With "METHOD=dbg make echo"?

$ METHOD=dbg make echo | grep O2
-g -O2
-g -O2

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to