public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Nathan Chancellor <nathan@kernel.org>,
	kernel test robot <lkp@intel.com>
Subject: Re: [linuxppc:next-test 85/129] arch/powerpc/xmon/xmon.c:489:12: error: stack frame size (2160) exceeds limit (2048) in 'xmon_core'
Date: Wed, 30 Aug 2023 09:29:39 +1000	[thread overview]
Message-ID: <87r0nlxw9o.fsf@mail.lhotse> (raw)
In-Reply-To: <CAKwvOdkO77jDijPwqkQJz6bGhjm5-3xWkTXbaxtXL8eZsqTi3g@mail.gmail.com>

Nick Desaulniers <ndesaulniers@google.com> writes:
> On Sun, Aug 27, 2023 at 4:32 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> Nick Desaulniers <ndesaulniers@google.com> writes:
>> > On Fri, Aug 25, 2023 at 12:17 PM kernel test robot <lkp@intel.com> wrote:
>> >>
>> >> tree:   https://github.com/linuxppc/linux next-test
>> >> head:   c37b6908f7b2bd24dcaaf14a180e28c9132b9c58
>> >> commit: 7f3c5d099b6f8452dc4dcfe4179ea48e6a13d0eb [85/129] Revert "powerpc/xmon: Relax frame size for clang"
>> >> config: powerpc64-randconfig-r006-20230825 (https://download.01.org/0day-ci/archive/20230826/202308260344.Vc4Giuk7-lkp@intel.com/config)
>> >> compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
>> >
>> > Hi Michael,
>> > Given this report and
>> > https://github.com/ClangBuiltLinux/linux/issues/252#issuecomment-1690371256,
>> > it seems that it's still possible to trigger this warning (and build
>> > failure with CONFIG_WERROR). Is it possible to drop my patch at this
>> > point?
>>
>> It's too late to drop it, so we'd need to do a revert.
>
> Np. Sent: https://lore.kernel.org/llvm/20230828-ppc_rerevert-v1-1-74f55b818907@google.com/

Thanks.

>> But rather than just a straight revert maybe we can do something that's
>> more tightly focused, ie. just to specific Clang versions?
>
> Seeing as the bot found a randconfig, I'm not confident that a version
> check would be enough at this point.

Yeah fair enough.

> Also, quite a few fires this Monday morning. I'd rather back this out
> entirely and revisit it another day.  I thought it would be a simple
> revert; obviously not!

No worries.

cheers

      reply	other threads:[~2023-08-29 23:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 19:16 [linuxppc:next-test 85/129] arch/powerpc/xmon/xmon.c:489:12: error: stack frame size (2160) exceeds limit (2048) in 'xmon_core' kernel test robot
2023-08-25 20:09 ` Nick Desaulniers
2023-08-27 11:32   ` Michael Ellerman
2023-08-28 17:39     ` Nick Desaulniers
2023-08-29 23:29       ` Michael Ellerman [this message]

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=87r0nlxw9o.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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