> > >> It would be isolated to target-specific logic in target-specific parts of >> the toolchain instead of inventing a new option that's basically "do what >> PNaCl wants" and then propagating it through the entire compiler. >> > > Clang currently supports le32 as a target. So it's not an issue of a > single "driver wrapper". We purposefully keep PNaCl as open as possible, > and other developers and toolchain writers may use this target to generate > PNaCl bitcode or something similar with Clang. > > > I'm not asking you to wrap the driver. I'm asking you to change clang's > driver logic when targeting *-*-nacl to use the existing logic to suppress > builtin treatment of functions. >
OK, I'll take a look at the driver logic and try to see if I can come up with an alternative patch. Eli
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
