This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/28515] CFLAGS not propagated, resulting in object mismatch
- From: "skunk at iskunk dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Aug 2006 08:32:36 -0000
- Subject: [Bug bootstrap/28515] CFLAGS not propagated, resulting in object mismatch
- References: <bug-28515-8784@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #12 from skunk at iskunk dot org 2006-08-06 08:32 -------
(In reply to comment #10)
> Passing -xarch=v9 to the compiler makes it a different compiler in essence, one
> that creates object files that are incompatible with the output of the default
> compiler. It also changes the operation of the linker. That makes the flag
> quite different from other compiler flags.
That's a fairly slippery slope. Does -KPIC/-fPIC/etc. make cc a different
compiler? -g/-O? -g/-pg? (Yes, the linker might be able to handle those
combinations, but you may end up with a Frankenbinary that fails unpredictably
at run-time.) Where do you draw the line?
That's beside the point, even. "$CC $CFLAGS" may produce something incompatible
with "$CC" alone---and yes, it is as if the two are completely different
compilers---but ***why*** are you using CC alone, without CFLAGS, in the first
place? Can someone please explain this to me?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28515