From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-snps-arc@lists.infradead.org,
Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
Michal Marek <mmarek@suse.cz>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARC: build: Turn off -Wmaybe-uninitialized for ARC gcc 4.8
Date: Fri, 18 Mar 2016 16:13:28 +0530 [thread overview]
Message-ID: <56EBDBD0.6090001@synopsys.com> (raw)
In-Reply-To: <3287558.oO5rz13nxZ@wuerfel>
On Friday 18 March 2016 03:59 PM, Arnd Bergmann wrote:
> On Friday 18 March 2016 15:50:11 Vineet Gupta wrote:
>> Sure, but I prefer this to be only for gcc 4.8 as this warning seems to be
>> healthy in small doses At least it keeps the door open for future discussion
>> with gcc guys !
>
> FWIW, testing on ARM with gcc-6.0 -O3, I also get tons of maybe-uninitialized
> warnings. It's unlikely that this is architecture specific or fixed in newer
> compiler versions.
So we disable this for good just like -Os.
What a shame - seemed like a reasonable safety net for programming errors.
>> The following nested construct actually works - does that look OK to you ?
>>
>> ARCH_CFLAGS += -O3 $(call cc-ifversion, -lt, 0408, $(call cc-disable-warning,maybe-uninitialized,))
>
> Yes, that seems ok.
There was typo actually -lt needed to be -eq
> I don't really understand why -O3 is needed though, maybe it's better to
> assume that it won't be needed in future gcc versions and do
Not sure what you mean, -O3 for triggering the warnings or -O3 in ARC makefile at all.
Assuming it's latter, this is how its been forever and was added consciously as
performance seemed better with -O3 than the default -O2.
>
> ARCH_CFLAGS += $(call cc-ifversion, -lt, 0408, -O3 $(call cc-disable-warning,maybe-uninitialized,))
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
WARNING: multiple messages have this Message-ID (diff)
From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] ARC: build: Turn off -Wmaybe-uninitialized for ARC gcc 4.8
Date: Fri, 18 Mar 2016 16:13:28 +0530 [thread overview]
Message-ID: <56EBDBD0.6090001@synopsys.com> (raw)
In-Reply-To: <3287558.oO5rz13nxZ@wuerfel>
On Friday 18 March 2016 03:59 PM, Arnd Bergmann wrote:
> On Friday 18 March 2016 15:50:11 Vineet Gupta wrote:
>> Sure, but I prefer this to be only for gcc 4.8 as this warning seems to be
>> healthy in small doses At least it keeps the door open for future discussion
>> with gcc guys !
>
> FWIW, testing on ARM with gcc-6.0 -O3, I also get tons of maybe-uninitialized
> warnings. It's unlikely that this is architecture specific or fixed in newer
> compiler versions.
So we disable this for good just like -Os.
What a shame - seemed like a reasonable safety net for programming errors.
>> The following nested construct actually works - does that look OK to you ?
>>
>> ARCH_CFLAGS += -O3 $(call cc-ifversion, -lt, 0408, $(call cc-disable-warning,maybe-uninitialized,))
>
> Yes, that seems ok.
There was typo actually -lt needed to be -eq
> I don't really understand why -O3 is needed though, maybe it's better to
> assume that it won't be needed in future gcc versions and do
Not sure what you mean, -O3 for triggering the warnings or -O3 in ARC makefile at all.
Assuming it's latter, this is how its been forever and was added consciously as
performance seemed better with -O3 than the default -O2.
>
> ARCH_CFLAGS += $(call cc-ifversion, -lt, 0408, -O3 $(call cc-disable-warning,maybe-uninitialized,))
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <linux-snps-arc@lists.infradead.org>,
Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
Michal Marek <mmarek@suse.cz>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
<linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARC: build: Turn off -Wmaybe-uninitialized for ARC gcc 4.8
Date: Fri, 18 Mar 2016 16:13:28 +0530 [thread overview]
Message-ID: <56EBDBD0.6090001@synopsys.com> (raw)
In-Reply-To: <3287558.oO5rz13nxZ@wuerfel>
On Friday 18 March 2016 03:59 PM, Arnd Bergmann wrote:
> On Friday 18 March 2016 15:50:11 Vineet Gupta wrote:
>> Sure, but I prefer this to be only for gcc 4.8 as this warning seems to be
>> healthy in small doses At least it keeps the door open for future discussion
>> with gcc guys !
>
> FWIW, testing on ARM with gcc-6.0 -O3, I also get tons of maybe-uninitialized
> warnings. It's unlikely that this is architecture specific or fixed in newer
> compiler versions.
So we disable this for good just like -Os.
What a shame - seemed like a reasonable safety net for programming errors.
>> The following nested construct actually works - does that look OK to you ?
>>
>> ARCH_CFLAGS += -O3 $(call cc-ifversion, -lt, 0408, $(call cc-disable-warning,maybe-uninitialized,))
>
> Yes, that seems ok.
There was typo actually -lt needed to be -eq
> I don't really understand why -O3 is needed though, maybe it's better to
> assume that it won't be needed in future gcc versions and do
Not sure what you mean, -O3 for triggering the warnings or -O3 in ARC makefile at all.
Assuming it's latter, this is how its been forever and was added consciously as
performance seemed better with -O3 than the default -O2.
>
> ARCH_CFLAGS += $(call cc-ifversion, -lt, 0408, -O3 $(call cc-disable-warning,maybe-uninitialized,))
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-03-18 10:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 8:46 [PATCH] ARC: build: Turn off -Wmaybe-uninitialized for ARC gcc 4.8 Vineet Gupta
2016-03-18 8:46 ` Vineet Gupta
2016-03-18 8:46 ` Vineet Gupta
2016-03-18 9:52 ` Arnd Bergmann
2016-03-18 9:52 ` Arnd Bergmann
2016-03-18 10:20 ` Vineet Gupta
2016-03-18 10:20 ` Vineet Gupta
2016-03-18 10:20 ` Vineet Gupta
2016-03-18 10:29 ` Arnd Bergmann
2016-03-18 10:29 ` Arnd Bergmann
2016-03-18 10:43 ` Vineet Gupta [this message]
2016-03-18 10:43 ` Vineet Gupta
2016-03-18 10:43 ` Vineet Gupta
2016-03-18 12:13 ` Arnd Bergmann
2016-03-18 12:13 ` Arnd Bergmann
2016-03-18 13:01 ` Vineet Gupta
2016-03-18 13:01 ` Vineet Gupta
2016-03-18 13:01 ` Vineet Gupta
2016-03-18 13:41 ` Arnd Bergmann
2016-03-18 13:41 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56EBDBD0.6090001@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mmarek@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.