mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>
Cc: Marco Elver <elver@google.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Kees Cook <kees@kernel.org>, Jaegeuk Kim <jaegeuk@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.2-rc3
Date: Mon, 9 Jan 2023 15:32:59 -0800	[thread overview]
Message-ID: <38fdb883-307f-f86a-2e04-80be7480c5ff@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wgg0hqiU5M3ExJdSNjx+BzDEC_fH7H_Rb0h_uykavg=Fw@mail.gmail.com>

On 1/9/23 15:14, Linus Torvalds wrote:
> On Mon, Jan 9, 2023 at 4:43 PM Vlastimil Babka <vbabka@suse.cz> wrote:
>>
>> On 1/9/23 23:18, Linus Torvalds wrote:
>>>
>>> Does anybody remember - what was the compiler version again and what
>>> do we need to disable?
>>
>> Guenter reported that "The problem is seen with gcc 11.3.0, but not with gcc
>> 12.2.0 nor with gcc 10.3.0."
>>
>> https://lore.kernel.org/all/20221227002941.GA2691687@roeck-us.net/
>>
>> Kees said it's -Warray-bounds, already disabled on gcc 12 for other reasons:
>>
>> https://lore.kernel.org/all/D8BDBF66-E44C-45D4-9758-BAAA4F0C1998@kernel.org/
> 
> Thanks.
> 
> I added a GCC11_NO_ARRAY_BOUNDS symbol to match the existing
> GCC12_NO_ARRAY_BOUNDS one, and to half-way document this thing.
> 
> I obviously don't see this warning myself, so my commit is "blind",
> but looks completely obvious.
> 
> Famous last words.
> 

Tested working.

Guenter


  reply	other threads:[~2023-01-09 23:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-08 18:06 Linus Torvalds
2023-01-09  9:01 ` Build regressions/improvements in v6.2-rc3-8-g1fe4fd6f5cad346e Geert Uytterhoeven
2023-01-09 17:47 ` Linux 6.2-rc3 Guenter Roeck
2023-01-09 22:18   ` Linus Torvalds
2023-01-09 22:29     ` Marco Elver
2023-01-09 22:34       ` Linus Torvalds
2023-01-09 22:43     ` Vlastimil Babka
2023-01-09 23:14       ` Linus Torvalds
2023-01-09 23:32         ` Guenter Roeck [this message]
2023-01-09 23:14     ` Guenter Roeck
2023-01-10 10:44     ` Peter Zijlstra
2023-01-10 11:32       ` Linus Torvalds

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=38fdb883-307f-f86a-2e04-80be7480c5ff@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=elver@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®