diff options
| author | Bruno Cardoso Lopes <bruno.cardoso@gmail.com> | 2016-05-27 20:43:00 +0000 |
|---|---|---|
| committer | Bruno Cardoso Lopes <bruno.cardoso@gmail.com> | 2016-05-27 20:43:00 +0000 |
| commit | 681d71721907b63a0462a1096fdf2f477ab0f326 (patch) | |
| tree | 191346bcfaaf2e90e76e9edb8b7091bacc63a8cd /llvm/test/Transforms/LoopVectorize/multi-use-reduction-bug.ll | |
| parent | 88a7892a0726a0f39910eacb2c2a1ef648803de7 (diff) | |
| download | bcm5719-llvm-681d71721907b63a0462a1096fdf2f477ab0f326.tar.gz bcm5719-llvm-681d71721907b63a0462a1096fdf2f477ab0f326.zip | |
[Driver] Fix driver support for color diagnostics
Diagnostics that happen during driver time do not have color output support
unless -fcolor-diagonostic is explicitly passed into the driver. This is not a
problem for cc1 since dianostic arguments are properly handled and color is
enabled by default if the terminal supports it.
Make the driver behave like CC1. There are tests that already check for these
flags, but for the color itself there's no sensible way to test it.
Differential Revision: http://reviews.llvm.org/D20404
rdar://problem/26290980
llvm-svn: 271042
Diffstat (limited to 'llvm/test/Transforms/LoopVectorize/multi-use-reduction-bug.ll')
0 files changed, 0 insertions, 0 deletions
