Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #148879

Re: Warning in LLVM Clang

From Mehdi Amini <atorrses@gmail.com>
Newsgroups comp.lang.c
Subject Re: Warning in LLVM Clang
Date 2020-01-09 17:49 +0330
Organization A noiseless patient Spider
Message-ID <qv7cp3$47h$1@dont-email.me> (permalink)
References (3 earlier) <87zhezjpzn.fsf@bsb.me.uk> <qv4k2e$ubn$1@dont-email.me> <qv4nui$k6m$1@dont-email.me> <qv779f$48g$1@dont-email.me> <qv7a56$kbk$1@dont-email.me>

Show all headers | View raw


On 1/9/20 5:04 PM, David Brown wrote:
> On 09/01/2020 13:45, Mehdi Amini wrote:
>> On 1/8/20 5:41 PM, David Brown wrote:
>>> On 08/01/2020 14:05, Mehdi Amini wrote:
>>>> On 1/7/20 6:03 PM, Ben Bacarisse wrote:
>>>>> Mehdi Amini <atorrses@gmail.com> writes:
>>>>>
>>>>>> On 1/6/20 7:28 PM, Ben Bacarisse wrote:

[...]

> 
> You are using clang-specific pragmas, then compiling with gcc with the
> warning for unknown pragmas enabled.  The compiler is giving you the
> warning you asked for.
> 
> Your choices include:
> 
> 1. Disable the "unknown pragma" warning (gcc -Wall -Wno-unknown-pragmas).
> 
> 2. Compile with clang.
> 
> 3. Change the clang-specific pragmas to gcc-specific equivalents:
> 
> 	#pragma GCC diagnostic warning "-Wall"
> 
> (clang might happily accept that too - it accepts a fair number of
> gcc-specific extensions.)
> 
> 4. Use conditional compilation testing compiler type, and give
> appropriate pragmas for different compilers.
> 
> 5. Drop the pragma entirely, and put the flags in the builder (makefile,
> cmake, or whatever).
> 
> 

Can I change the Makefile as I originally intended , that is , is it
safe to change these :

CC = gcc
CCDEPMODE = depmode=gcc3
CFLAGS =   -Wall -Wno-parentheses

to

CC = gcc
CCDEPMODE = depmode=gcc3
CFLAGS =

Then enable warnings on a specific part of code with what you said ? or 
even other warnings like -Wextra ?

#pragma GCC diagnostic warning "-Wall"

-- 
www.my-c-codes.com/

Farewell.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-06 17:57 +0330
  Warning in LLVM Clang chad <cdalten@gmail.com> - 2020-01-06 07:47 -0800
  Re: Warning in LLVM Clang Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-01-06 15:58 +0000
    Re: Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-07 15:32 +0330
      Which compiler is it, anyway??? (Was: Warning in LLVM Clang) gazelle@shell.xmission.com (Kenny McCormack) - 2020-01-07 12:58 +0000
      Re: Warning in LLVM Clang Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-01-07 14:33 +0000
        Re: Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-08 16:35 +0330
          Re: Warning in LLVM Clang David Brown <david.brown@hesbynett.no> - 2020-01-08 15:11 +0100
            Re: Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-09 16:15 +0330
              Re: Warning in LLVM Clang David Brown <david.brown@hesbynett.no> - 2020-01-09 14:34 +0100
                Re: Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-09 17:49 +0330
                Re: Warning in LLVM Clang Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-01-09 19:35 +0000
                Re: Warning in LLVM Clang David Brown <david.brown@hesbynett.no> - 2020-01-10 10:28 +0100
                Re: Warning in LLVM Clang Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-01-10 12:39 +0000
                Re: Warning in LLVM Clang Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-01-10 12:57 +0000
                Re: Warning in LLVM Clang Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-01-10 13:23 +0000
                Re: Warning in LLVM Clang David Brown <david.brown@hesbynett.no> - 2020-01-10 14:09 +0100
                Re: Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-10 16:45 +0330
                Re: Warning in LLVM Clang Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-01-10 13:20 +0000
                Re: Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-10 17:20 +0330
                Re: Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-10 17:24 +0330
                Re: Warning in LLVM Clang Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-01-10 23:52 +0000
                Re: Warning in LLVM Clang scott@slp53.sl.home (Scott Lurndal) - 2020-01-10 15:29 +0000
                Re: Warning in LLVM Clang Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-01-10 23:28 +0000
                Re: Warning in LLVM Clang Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-01-11 14:21 +0000
              Re: Warning in LLVM Clang James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-01-09 22:08 -0500
                Not exactly an "alias", but that's just being a CLC pedant... (Was: Warning in LLVM Clang) gazelle@shell.xmission.com (Kenny McCormack) - 2020-01-10 09:52 +0000
                Re: Not exactly an "alias", but that's just being a CLC pedant... (Was: Warning in LLVM Clang) David Brown <david.brown@hesbynett.no> - 2020-01-10 11:26 +0100
                Re: Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-10 16:48 +0330
                Re: Warning in LLVM Clang Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-01-10 09:34 -0800
                Re: Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-11 14:41 +0330
  Re: Warning in LLVM Clang Guillaume <message@bottle.org> - 2020-01-06 17:23 +0100
    Re: Warning in LLVM Clang Mehdi Amini <atorrses@gmail.com> - 2020-01-07 15:39 +0330

csiph-web