On Mon, Jul 18, 2011 at 21:00, Gabriel Charette <gch...@google.com> wrote:
> We probably only want to enforce this for a subset of the flags (i.e. > we don't care about flags like -Wall and stuff like that, but only > about the flags actually affecting the binary output). In principle, this is no different than mixing and matching .o files that have been compiled with different options. As much as possible, we want to punt this up to the build system. Introducing errors/warnings when we detect incompatible flags that affect parsing is OK. We already do this for pre-processor macros, for instance. Diego.
