Is the Tornado tag file one that you build and placed under "C" Tag Files?
If so then it will be used for all "C" code. I would suggest removing it from there and making it an auto-updated tag file for the workspace(s) that use Tornado.
The set of tag files used by context tagging is as follows:
1) Your workspace tag file if the current file is the same language.
2) Any "auto-updated" tag files for your current workspace
again, only if the current file is the same language.
3) The Language specific (extension specific in 12.0.2) tag files
for the current file (see Tag Files dialog)
4) If the current file is C or ANSI-C, your "C" compiler tag file,
using the setting in the project, (which can fall back to the default)
5) If the current file is Java, your "Java" compiler tag file,
using the setting in the project, (which, again, can fall back to the default)
I know, it's complicated, somewhat more so that I would like, and ironically, all I ever get are more requests to make it even more complicated (per-project tag files, per-configuration tag files, tag files that only work on Tuesdays, tag files that rebuild when I get up to refill my coffee, you get the picture).