TIFF is a very versatile container format for various image-streams. It can encode multi-images(likes layers), with different compression (losseless, JPEG etc) and tiled images to read/write efficiently big images e.g. for astronomy, pathology (microscopy). It is the standard for archiving images.
First, this is obviously a problem with the browser ("I can't view a common image standard!"), not the image format (it may have other problems, but "third party software isn't supporting this format" isn't a real problem).
Second, assuming your goal is to study the picture, of course you want to save it to disk.
If you do static analysis on Step 2 (ie on the AST) then you only need the Front-end of your compiler.
Clang/LLVM is much more modular, library oriented.(which is why the Google engineer wanted to switch to it). You can just link to the needed front-end and do the static analysis without generating the LLVM bytecode.
So yes, you could install a static-analyzer without the whole compiler.
So yes, you could install a static-analyzer without the whole compiler.
You can install a static analyzer without the whole compiler, but not gcc's static analyzer. I assumed "the static analyzer" that sp332 was talking about was specifically gcc's, not any generic static analyzer.
Having read the paper, it seems its more specialized to cisco IOS config files - they're building a library of patterns you can match against, the paper doesn't explain how you can add your own. And it does seem to be CFG rather than PEG - there's a separate token library.
Ward's work looks more usably generic than this, it's not cited so I presume they weren't aware of it.