unrecognized option: -fsave-memoized
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
Menu
▾
▴
This happened with DevC 4.9.9.2:
Create new Project
select Console Application (C Project)
Save main.c as-is
Compile (OK so far)
Rebuild all (OK so far)
Menu: Project ->Project options
(no changes, just click OK)
Rebuild All: fails with...
cc1.exe: error: unrecognized command line option "-fsave-memoized"
The error is also reported wrong in the 'Compiler'
tab, where the path to cc1.exe is wrong (project
directory instead of location somewhere in the
DevC install dir), but that just besides.
What is this -fsave-memoized option for, and
is there a way to tell DevC not to use it ?
@[nobody]:
Look above, there IS a path:
The 'compile' tab displays:
E:\PC_devc_test\cc1.exe (my project dir!)
Should be:
E:\dev-cpp\<somewhere>\cc1.exe (the devc dir)
However, just a minor quirk i don't really care..
actually i was saying that it was devs interface at fault at nothing crucial. in other word nothing to worry about beyond as you say the quirk.
Chect your compile options and project options, a switch has gotten flipped somewhere.
Please not also that you should post your compile log - its on the tab labeled compile log and the right mouse button brings up the copy menu - in full, rather than excerpting the errors. If you have a ton of errors, start from the beginning and copy through the first 5 or so errors.
Wayne
Well the error was a snap from the compile log,
where the 'wrong report' was seen in the compiler
tab. I'll soon re-install DevC completely, changing
nothing and then retry step-by-step to isolate
the problem. Hang on.. :)
"I'll soon re-install DevC completely"
Make sure you follow the directions for a clean uninstall that can be found in the Please Read Before Posting a Question section - configuration files which are not deleted during uninstall and are in hidden folders will cause issues like yours to come back.
Now, you seem to have missed the point about the compile log. NEVER excerpt the error from the log. Post the log. The reason? There is a TON of useful information to help debug your setup. When you excerpt just the error, you throw that away.
Wayne
After a few re-installs, i can now re-construct
the exact reason for the error.
I've created a new C project (console app) while
the option "Compiler --- C++ Compiler --- use
heuristics to compile faster" was turned on.
Even with a C project (no C++ and with just
main.c), this C++ option turned out to be the
problem. Never thought that this could have
any influence there so i didn't mention..
After turning this option off and creating
the project again, everything went fine.
So this is likely to be a bug?
However, glad to be able to go on.
Oliver 'Bloody' Lange.
Before i forget:
Here's the compile log with the error (double
quotes replaced by single quotes because of
this forum...):
Compiler: Default compiler
Building Makefile: 'E:\PC_devc_test\Makefile.win'
Executing make clean
rm -f main.o _devc_test.exe
gcc.exe -c main.c -o main.o -I'E:/Dev-Cpp/include' -fsave-memoized -fexpensive-optimizations -O3
cc1.exe: error: unrecognized command line option '-fsave-memoized'
make.exe: *** [main.o] Error 1
Execution terminated
in the 'compiler' tab, the wrong path to cc1.exe
is shown (assuming that devc does not copy
cc1.exe over to the makefile location):
cc1.exe E:\PC_devc_test\cc1.exe unrecognized command line option '-fsave-memoized'
The path to cc1.exe should be E:\dev-cpp\and-so-on .. (if i understand this right)
Oliver 'Bloody' Lange.
yea, i would say this is a bug.
--memoize-lookups
-fmemoize-lookups
--save-memoized
-fsave-memoized
were removed from gcc during 2.95 finalization.
make by its nature shows the command as it is interpreted. no path used in the command in the makefile no path in the output.
I have also seen some people who swear they didn't turn an option on (usually the dollar sign in identifiers), yet it is on....
Wayne