public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "byteslice at airmail dot cc" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105420] Bogus -Warray-bounds with non-compile time-constant variable Date: Fri, 29 Apr 2022 11:42:32 +0000 [thread overview] Message-ID: <bug-105420-4-IInLaHD0jL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105420-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105420 --- Comment #2 from Liam White <byteslice at airmail dot cc> --- Created attachment 52906 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52906&action=edit Preprocessed source The first attachment is automatically and manually reduced from the following source: ResultCode KThread::Initialize(KThreadFunction func, uintptr_t arg, VAddr user_stack_top, s32 prio, s32 virt_core, KProcess* owner, ThreadType type) { // Assert parameters are valid. ASSERT((type == ThreadType::Main) || (type == ThreadType::Dummy) || (Svc::HighestThreadPriority <= prio && prio <= Svc::LowestThreadPriority)); ASSERT((owner != nullptr) || (type != ThreadType::User)); ASSERT(0 <= virt_core && virt_core < static_cast<s32>(Common::BitSize<u64>())); // Convert the virtual core to a physical core. const s32 phys_core = Core::Hardware::VirtualToPhysicalCoreMap[virt_core]; ASSERT(0 <= phys_core && phys_core < static_cast<s32>(Core::Hardware::NUM_CPU_CORES)); // ... } And it produces this compiler error (compile this preprocessed source with -O2 -Werror=array-bounds -std=gnu++20): In static member function ‘static constexpr _Tp& std::__array_traits<_Tp, _Nm>::_S_ref(const _Tp (&)[_Nm], std::size_t) [with _Tp = int; long unsigned int _Nm = 64]’, inlined from ‘constexpr const std::array<_Tp, _Nm>::value_type& std::array<_Tp, _Nm>::operator[](size_type) const [with _Tp = int; long unsigned int _Nm = 64]’ at k_thread.cpp:59748:25, inlined from ‘ResultCode Kernel::KThread::Initialize(Kernel::KThreadFunction, uintptr_t, VAddr, s32, s32, Kernel::KProcess*, Kernel::ThreadType)’ at k_thread.cpp:102280:77: k_thread.cpp:59638:36: error: array subscript 64 is above array bounds of ‘std::__array_traits<int, 64>::_Type’ {aka ‘const int [64]’} [-Werror=array-bounds] 59638 | { return const_cast<_Tp&>(__t[__n]); } | ~~~^ k_thread.cpp: In member function ‘ResultCode Kernel::KThread::Initialize(Kernel::KThreadFunction, uintptr_t, VAddr, s32, s32, Kernel::KProcess*, Kernel::ThreadType)’: k_thread.cpp:77557:51: note: while referencing ‘Core::Hardware::VirtualToPhysicalCoreMap’ 77557 | constexpr std::array<s32, Common::BitSize<u64>()> VirtualToPhysicalCoreMap{ | ^~~~~~~~~~~~~~~~~~~~~~~~ cc1plus: some warnings being treated as errors I generally believe that this is a bug in the compiler as the array is similarly never accessed with the constant value 64.
prev parent reply other threads:[~2022-04-29 11:42 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-28 13:21 [Bug tree-optimization/105420] New: " byteslice at airmail dot cc 2022-04-29 6:26 ` [Bug tree-optimization/105420] " rguenth at gcc dot gnu.org 2022-04-29 11:42 ` byteslice at airmail dot cc [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=bug-105420-4-IInLaHD0jL@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).