Date: Sun, 20 Jan 2013 15:26:44 +0530 From: Dhiru Kholia <dhiru.kholia@...il.com> To: john-dev@...ts.openwall.com Subject: Re: new clang 3.2 warnings On Sun, Jan 20, 2013 at 3:08 PM, Frank Dittrich <frank_dittrich@...mail.com> wrote: > On 01/20/2013 04:35 AM, Dhiru Kholia wrote: >> I am getting tons of warnings which look like "clang: warning: >> argument '-faddress-sanitizer' is deprecated, use '-fsanitize=address' >> instead" when using clang 3.2. >> >> These warnings are harmless (but ugly) and are emitted only during >> *-clang-debug target builds. >> >> Is adding something like "HAVE_CLANG_3_2" to Makefile the only >> solution to fix this problem? > > I am getting warnings > > clang: warning: argument unused during compilation: '-faddress-sanitizer' > > when building with > > $ clang --version > clang version 2.9 (tags/RELEASE_29/final) > Target: i386-redhat-linux-gnu > Thread model: posix > > I just assumed that my clang version was too old to know this switch. > Since only the -clang-debug target was affected, I didn't care. > > I would prefer -clang-debug just using the option name that is required > for the newest clang version(s), instead of having to adjust one more > config variable. > But when I change the option name in Makefile, I get > clang: warning: argument unused during compilation: '-fsanitize=address' > instead, for 2.9 and for 3.1. > > This is bad. May be HAVE_CLANG_3_2 is a good enough solution right now? > How widespread is clang 3.2? Fedora 18 still uses 3.1. I don't think clang 3.2 is very widespread. I have it since I run Arch Linux which is a rolling release distribution. So, we have *two* problems with clang-debug targets, clang being too old or clang being too new. -- Dhiru
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.