public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug driver/39293] New: -save-temps does not follow the -o option and instead puts the temp file in the current directory
@ 2009-02-24 17:47 meissner at linux dot vnet dot ibm dot com
2009-02-24 18:10 ` [Bug driver/39293] " pinskia at gcc dot gnu dot org
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: meissner at linux dot vnet dot ibm dot com @ 2009-02-24 17:47 UTC (permalink / raw)
To: gcc-bugs
I was building Spec 2006 with a powerpc64-linux cross compiler using the
-save-temps option so that I could do some analysis on the generated code.
Unfortunately, if I use -j4 in the make for the spec build, the test cactusADM
does not build. I traced this down to there were several Startup.c files in
different directories, and the spec make uses -o to put the resulting objects
in different directories:
<gcc>/gcc <flags> -o PUGH/Startup.o PUGH/Startup.c
<gcc>/gcc <flags> -o IOUtil/Startup.o IOUtil/Startup.c
<gcc>/gcc <flags> -o BenchADMsrc/Startup.o BenchADMsrc/Startup.c
<gcc>/gcc <flags> -o CartGrid3D/Startup.o CartGrid3D/Startup.c
...
As luck would have it, make decided to compile several of of the Startup.c's at
the same time, and since they wrote the files in the current directory, they
overwrote each other, and the assembler complained about illegal input.
--
Summary: -save-temps does not follow the -o option and instead
puts the temp file in the current directory
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: meissner at linux dot vnet dot ibm dot com
GCC build triplet: x86_64-gnu-linux
GCC host triplet: x86_64-gnu-linux
GCC target triplet: powerpc64-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39293
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug driver/39293] -save-temps does not follow the -o option and instead puts the temp file in the current directory 2009-02-24 17:47 [Bug driver/39293] New: -save-temps does not follow the -o option and instead puts the temp file in the current directory meissner at linux dot vnet dot ibm dot com @ 2009-02-24 18:10 ` pinskia at gcc dot gnu dot org 2009-02-24 19:08 ` joseph at codesourcery dot com ` (3 subsequent siblings) 4 siblings, 0 replies; 6+ messages in thread From: pinskia at gcc dot gnu dot org @ 2009-02-24 18:10 UTC (permalink / raw) To: gcc-bugs ------- Comment #1 from pinskia at gcc dot gnu dot org 2009-02-24 18:10 ------- Here at Sony we added -save-temps-o option which does this. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pinskia at gcc dot gnu dot | |org Severity|normal |enhancement http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39293 ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug driver/39293] -save-temps does not follow the -o option and instead puts the temp file in the current directory 2009-02-24 17:47 [Bug driver/39293] New: -save-temps does not follow the -o option and instead puts the temp file in the current directory meissner at linux dot vnet dot ibm dot com 2009-02-24 18:10 ` [Bug driver/39293] " pinskia at gcc dot gnu dot org @ 2009-02-24 19:08 ` joseph at codesourcery dot com 2009-02-28 1:01 ` meissner at linux dot vnet dot ibm dot com ` (2 subsequent siblings) 4 siblings, 0 replies; 6+ messages in thread From: joseph at codesourcery dot com @ 2009-02-24 19:08 UTC (permalink / raw) To: gcc-bugs ------- Comment #2 from joseph at codesourcery dot com 2009-02-24 19:07 ------- Subject: Re: New: -save-temps does not follow the -o option and instead puts the temp file in the current directory I've also found this to be a pain when working on glibc, where compilation commands are run from subdirectories of the source directory so using -save-temps causes the temporary files to be put in the source directory, after which the glibc build system can end up using them for future builds in preference to the actual source files. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39293 ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug driver/39293] -save-temps does not follow the -o option and instead puts the temp file in the current directory 2009-02-24 17:47 [Bug driver/39293] New: -save-temps does not follow the -o option and instead puts the temp file in the current directory meissner at linux dot vnet dot ibm dot com 2009-02-24 18:10 ` [Bug driver/39293] " pinskia at gcc dot gnu dot org 2009-02-24 19:08 ` joseph at codesourcery dot com @ 2009-02-28 1:01 ` meissner at linux dot vnet dot ibm dot com 2009-04-02 20:45 ` meissner at gcc dot gnu dot org 2009-04-29 12:08 ` bje at gcc dot gnu dot org 4 siblings, 0 replies; 6+ messages in thread From: meissner at linux dot vnet dot ibm dot com @ 2009-02-28 1:01 UTC (permalink / raw) To: gcc-bugs ------- Comment #3 from meissner at linux dot vnet dot ibm dot com 2009-02-28 01:01 ------- Created an attachment (id=17374) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17374&action=view) This patch fixes -save-temps so that it puts the temp file in the output directory rather than the current directory -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39293 ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug driver/39293] -save-temps does not follow the -o option and instead puts the temp file in the current directory 2009-02-24 17:47 [Bug driver/39293] New: -save-temps does not follow the -o option and instead puts the temp file in the current directory meissner at linux dot vnet dot ibm dot com ` (2 preceding siblings ...) 2009-02-28 1:01 ` meissner at linux dot vnet dot ibm dot com @ 2009-04-02 20:45 ` meissner at gcc dot gnu dot org 2009-04-29 12:08 ` bje at gcc dot gnu dot org 4 siblings, 0 replies; 6+ messages in thread From: meissner at gcc dot gnu dot org @ 2009-04-02 20:45 UTC (permalink / raw) To: gcc-bugs ------- Comment #4 from meissner at gcc dot gnu dot org 2009-04-02 20:45 ------- Subject: Bug 39293 Author: meissner Date: Thu Apr 2 20:45:26 2009 New Revision: 145470 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145470 Log: [PATCH, committed] Add -save-temps=obj, PR 39293 Modified: trunk/gcc/ChangeLog trunk/gcc/doc/invoke.texi trunk/gcc/gcc.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39293 ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug driver/39293] -save-temps does not follow the -o option and instead puts the temp file in the current directory 2009-02-24 17:47 [Bug driver/39293] New: -save-temps does not follow the -o option and instead puts the temp file in the current directory meissner at linux dot vnet dot ibm dot com ` (3 preceding siblings ...) 2009-04-02 20:45 ` meissner at gcc dot gnu dot org @ 2009-04-29 12:08 ` bje at gcc dot gnu dot org 4 siblings, 0 replies; 6+ messages in thread From: bje at gcc dot gnu dot org @ 2009-04-29 12:08 UTC (permalink / raw) To: gcc-bugs ------- Comment #5 from bje at gcc dot gnu dot org 2009-04-29 12:08 ------- Fixed for 4.5. -- bje at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED Target Milestone|--- |4.5.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39293 ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-04-29 12:08 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2009-02-24 17:47 [Bug driver/39293] New: -save-temps does not follow the -o option and instead puts the temp file in the current directory meissner at linux dot vnet dot ibm dot com 2009-02-24 18:10 ` [Bug driver/39293] " pinskia at gcc dot gnu dot org 2009-02-24 19:08 ` joseph at codesourcery dot com 2009-02-28 1:01 ` meissner at linux dot vnet dot ibm dot com 2009-04-02 20:45 ` meissner at gcc dot gnu dot org 2009-04-29 12:08 ` bje at gcc dot gnu dot org
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).