Yes, I am aware of that feature of gcc. What I really want to do is
remove the other flags. Currently, the gcc command looks like:
gcc -fno-strict-aliasing -march=native -pipe -fwrapv -DNDEBUG -g -fwrapv
-O3 -Wall -Wstrict-prototypes -fPIC
-I/home/punarbasu/Installations/sage-5.2.trac/local/include/python2.7 -c
code_functions.c -o build/temp.linux-x86_64-2.7/code_functions.o
I want this to be reduced to
gcc -O0 -I....(rest of the command)
The main reason for doing so is that I am trying to track a bug, but
want to check everything without optimization and other flags first.
On 09/22/2012 06:58 PM, Volker Braun wrote:
GCC specifies that the last option takes effect on the command line. Its
common practice to append CFLAGS to override earlier ones. So gcc -O3
-O2 -O0 source.c compiles without optimization.
On Saturday, September 22, 2012 11:29:07 AM UTC+1, P Purkayastha wrote:
Hi,
Is there any way to change or remove all the compilation flags
provided to gcc while compiling cython code in Sage? Currently, I
have a setup.py file and I am running
||
sage -python setup.py build_ext --inplace
to compile cython code.
I tried providing custom CFLAGS, like CFLAGS="-O0", but it seems to
only get appended to the gcc command. I also tried exporting OPTS=""
(found this advice for python in a stackoverflow thread) but that
doesn't seem to help. Also tried the above in a "sage -sh"
environment and then calling python directly.
--
You received this message because you are subscribed to the Google
Groups "sage-support" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
Visit this group at http://groups.google.com/group/sage-support?hl=en.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
Visit this group at http://groups.google.com/group/sage-support?hl=en.
