linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Peter Xu <peterx@redhat.com>, Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: mm/gup.c:679:22: error: call to '__compiletime_assert_382' declared with 'error' attribute: BUILD_BUG failed
Date: Thu, 4 Apr 2024 12:42:12 +0200	[thread overview]
Message-ID: <CANiq72mVuYbOKmjFUXf5eTeS8a3RoruZfyYvw+_iN+tkd9HzSg@mail.gmail.com> (raw)

Hi Peter, Andrew,

I am not sure if this is one of the issues that Peter mentioned [1] to
be resolved or not eventually, but I have spotted this in the last
couple -next runs for a LLVM=1 loongarch64 defconfig build [2].

Hope that helps!

Cheers,
Miguel

[1] https://lore.kernel.org/all/ZgMzaMu7oILiNLcG@x1n/
[2]

mm/gup.c:679:22: error: call to '__compiletime_assert_382' declared
with 'error' attribute: BUILD_BUG failed
679 | unsigned long pfn = pud_pfn(pud);
| ^
./include/linux/pgtable.h:1887:23: note: expanded from macro 'pud_pfn'
1887 | #define pud_pfn(x) ({ BUILD_BUG(); 0; })
| ^
./include/linux/build_bug.h:59:21: note: expanded from macro 'BUILD_BUG'
59 | #define BUILD_BUG() BUILD_BUG_ON_MSG(1, "BUILD_BUG failed")
| ^
./include/linux/build_bug.h:39:37: note: expanded from macro 'BUILD_BUG_ON_MSG'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^
note: (skipping 1 expansions in backtrace; use
-fmacro-backtrace-limit=0 to see all)
././include/linux/compiler_types.h:448:2: note: expanded from macro
'_compiletime_assert'
448 | __compiletime_assert(condition, msg, prefix, suffix)
| ^
././include/linux/compiler_types.h:441:4: note: expanded from macro
'__compiletime_assert'
441 | prefix ## suffix(); \
| ^
<scratch space>:48:1: note: expanded from here
48 | __compiletime_assert_382
| ^
1 error generated.


             reply	other threads:[~2024-04-04 10:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 10:42 Miguel Ojeda [this message]
2024-04-04 11:57 ` Peter Xu
2024-04-05 13:21   ` Miguel Ojeda

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=CANiq72mVuYbOKmjFUXf5eTeS8a3RoruZfyYvw+_iN+tkd9HzSg@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jgg@nvidia.com \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.com \
    /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