Messages in this thread | | | Subject | Re: [PATCH 2/4] Core support for --combine -fwhole-program | From | David Woodhouse <> | Date | Thu, 24 Aug 2006 18:33:23 +0100 |
| |
On Thu, 2006-08-24 at 10:27 -0700, Josh Triplett wrote: > Would the generation and use of preprocessed source files ($x.c -> $x.i) > help solve the "standard CFLAGS" problem here, and allow a subsequent > single compilation of the entire kernel (sans modules) with --combine > -fwhole-program?
Not for stuff like CFLAGS_raid6altivec1.o := -maltivec -mabi-altivec
Stuff which is _purely_ #defines, such as... ncr53c8xx-flags-$(CONFIG_SCSI_ZALON) \ := -DCONFIG_NCR53C8XX_PREFETCH -DSCSI_NCR_BIG_ENDIAN \ -DCONFIG_SCSI_NCR53C8XX_NO_WORD_TRANSFERS CFLAGS_ncr53c8xx.o := $(ncr53c8xx-flags-y) $(ncr53c8xx-flags-m)
... can probably be done differently anyway.
It's not entirely unreasonable to treat files with their own CFLAGS just as we have to treat .S files -- compile them separately, then link.
-- dwmw2
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |