[cfe-dev] clang-tidy & SSE with GCC toolchain

[Daniel Evers via cfe-dev]

Hi @all,

Thanks again for all help - it turned out the problem was home-grown after all :(
Somewhere in the script to generate the compilation database, the GCC include were explicitly added. This brought in the problems. (seems like we needed this for an older version were clang was installed in a different directory than clang-tidy)

I fixed it to pass the Clang parameters as-is and all problems were gone... Same flags for clang-tidy and clang++ and it works as expected.

Sorry & thanks again!
Daniel

-----Original Message-----
From: Kim Gräsman [mailto:kim.grasman at gmail.com]
Sent: Freitag, 26. Januar 2018 11:12
To: Daniel Evers <Daniel.Evers at utimaco.com>
Cc: Csaba Raduly <rcsaba at gmail.com>; Craig Topper <craig.topper at gmail.com>; cfe-dev at lists.llvm.org
Subject: Re: [cfe-dev] clang-tidy & SSE with GCC toolchain

On Fri, Jan 26, 2018 at 10:36 AM, Daniel Evers via cfe-dev <cfe-dev at lists.llvm.org> wrote:
> Hi,
>
> Thanks for the tip. I checked the output and clang++ uses its own includes instead of the GCC headers.
> Does the compiler add some pre-defined include paths that the clang-based tools don't have by default?
>
> Clang-tidy at least doesn't complain about -gcc-toolchain ;-) But I'm not sure if it's relevant here.

There used to (not sure if it's still there) a special relative lookup for the builtins, something like $dirname(driver-binary)/../lib/clang-6.0/include. So if your clang-tidy is not in /usr/bin, it might not find the builtins.

- Kim


________________________________

Utimaco TS GmbH
Germanusstr. 4, D.52080 Aachen, Germany, Tel: +49-241-1696-0, www.utimaco.com
Seat: Aachen – Registergericht Aachen HRB 18923
VAT ID No.: DE 815 496 507
Managementboard: Malte Pollmann (Chairman) CEO, Dr. Frank J. Nellissen CFO

This communication is confidential. We only send and receive email on the basis of the terms set out at https://www.utimaco.com/en/e-mail-disclaimer/