public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106409] GCC with LTO: Warning: argument 1 value ‘18...615’ (SIZE_MAX) exceeds maximum object size Date: Wed, 17 May 2023 18:21:34 +0000 [thread overview] Message-ID: <bug-106409-4-DqhKa8HLc0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106409-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106409 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=80922 Ever confirmed|0 |1 Keywords| |lto Last reconfirmed|2022-07-22 00:00:00 |2023-05-17 Status|UNCONFIRMED |NEW --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I suspect the issue is for LTO we don't stream out the ignore part . Anyways confirmed, you can reproduce it with the following single file testcase: ``` typedef struct st_mysql_bind { int t; int t1; int t2; int t3; } bb; [[gnu::noipa]] void *f(unsigned long paramCount) { if (paramCount == 0) return nullptr; return new bb[paramCount](); } int main(void) { f(100); } ``` Compile it with `-flto -W -Wall -O2` and see the warning.
next prev parent reply other threads:[~2023-05-17 18:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-22 11:12 [Bug c++/106409] New: " lluis.alemany.puig at gmail dot com 2022-07-22 11:13 ` [Bug c++/106409] " lluis.alemany.puig at gmail dot com 2022-07-22 11:25 ` marxin at gcc dot gnu.org 2022-07-22 12:03 ` lluis.alemany.puig at gmail dot com 2022-07-25 18:29 ` [Bug tree-optimization/106409] " pinskia at gcc dot gnu.org 2023-05-17 18:21 ` pinskia at gcc dot gnu.org [this message] 2023-05-17 18:22 ` pinskia at gcc dot gnu.org 2023-05-17 18:38 ` [Bug tree-optimization/106409] GCC with LTO: Warning: argument 1 value ‘18...615’ (SIZE_MAX) exceeds maximum object size with new thiago at kde dot org 2023-05-17 18:47 ` pinskia at gcc dot gnu.org 2023-05-17 18:58 ` thiago at kde dot org
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-106409-4-DqhKa8HLc0@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).