On 4/25/08, Pavel Roskin <proski@xxxxxxx> wrote: > Quoting Marko Kreen <markokr@xxxxxxxxx>: > > Patch attached. > > NACK. $m64 is only set if "-m64" was explicitly passed to cgcc. > > It looks like cgcc code expect sparse to handle it, and sparse expects it > from cgcc. Do you mean the variables are not set? But they are: my $m32 = 0; my $m64 = 0; Or do you mean I cannot assume one of them as set, unless overrided on command line? But other sections (spact, i86, ppc) do exactly that? Or do you mean I cannot give extra -mXX arguement unless given by user? But as you said, sparse (by policy) wont follow platform default, but I want cgcc to follow it. How do I achieve that then? -- marko -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
