[llvm] r226248 - Use report_fatal_error instead of llvm_unreachable, so we don't crash on user input

Filipe Cabecinhas me at filcab.net
Fri Feb 6 14:06:32 PST 2015


I fixed it in r226986 ;-)
Thanks for noticing it, anyway.

  Filipe

On Fri, Feb 6, 2015 at 5:25 AM, Rafael EspĂ­ndola <rafael.espindola at gmail.com
> wrote:

> > Added: llvm/trunk/test/Bitcode/invalid.test
> > URL:
> http://llvm.org/viewvc/llvm-project/llvm/trunk/test/Bitcode/invalid.test?rev=226248&view=auto
> >
> ==============================================================================
> > --- llvm/trunk/test/Bitcode/invalid.test (added)
> > +++ llvm/trunk/test/Bitcode/invalid.test Thu Jan 15 22:54:12 2015
> > @@ -0,0 +1 @@
> > +RUN: not llvm-dis -disable-output %p/Inputs/invalid-pr20485.bc
>
> FileCheck for the message?
>
> Cheers,
> Rafael
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150206/3063623b/attachment.html>


More information about the llvm-commits mailing list