Suggested some improvements to the comments below. Generally, this makes sense, 
but I think you should also mention your end-goal in the commit log. I happen 
to know because we've chatted, and so this change makes sense to me, but others 
won't have that context.

For those reading the review log, the context is that there exist some embedded 
platforms which use specialized C derivatives and C compilers where Clang 
doesn't support their derivative yet. We'd like to add support for these 
platforms to Clang, but at least until we do, its useful if the toolchain for 
such an embedded target can detect special flags and dispatch to whatever 
embedded compiler is commonly used. This makes the Clang driver more of a 
drop-in replacement and starts us down the path of support.

Actually, Doug, it might be worth sending an email to cfe-dev with the overall 
plan you have here to support C-dialects on embedded platforms by dispatching 
to the vendor-provided SDK until Clang grows support for that dialect. There 
you can give an overview and hopefully that'll provide context for folks seeing 
these commits.


http://reviews.llvm.org/D10246

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/



_______________________________________________
cfe-commits mailing list
cfe-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

Reply via email to