Assuming the toolchain is installed correctly (no corrupt or missing files), a segfault in the compiler during compilation is never a reasonable response, as opposed to an orderly abnormal termination with an appropriate error message. It should always be considered a bug.
I would suggest filing a bug report with NVIDIA, using the form linked from the CUDA registered developer website. In my experience, there are rarely workarounds for bugs of this nature, but if you file a bug there is a chance the compiler team has a recommendation as to how to avoid it.
before you file a bug, update your system to CUDA 8 (production release) which should be 8.0.44 or something like that.
The error message you are reporting is a generic one that could happen with various different compiler issues. It’s almost certainly not due to a single issue that has been around since CUDA 2.0 and never fixed. So just because you are finding reports of that error message dating back to CUDA 2.0 does not mean that you are having the same underlying issue in the compiler that has never been fixed.
As a sanity check: are you able to successfully build the example programs that ship with CUDA? If so, that means the installed toolchain is functional, and it is extremely likely you are hitting a bug in the CUDAFE component of the CUDA toolchain.
For filing a bug report with NVIDIA, you would want to prepare the smallest possible self-contained code that reproduces the issue and attach that to the bug report. A single, short, source code file plus the nvcc commandline invocation that triggers the segfault would be ideal for this purpose.