public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107618] Incorrect diagnostics when using -Og, builtin_expect(), and function attribute "warning" or "error" Date: Fri, 11 Nov 2022 07:47:37 +0000 [thread overview] Message-ID: <bug-107618-4-JpM5vpkirR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107618-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107618 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Version|unknown |13.0 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Last reconfirmed| |2022-11-11 Keywords| |diagnostic Component|middle-end |tree-optimization Ever confirmed|0 |1 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- We diagnose because we see int main () { long int _2; <bb 2> [local count: 1073741824]: _2 = 0; if (_2 != 0) goto <bb 3>; [10.00%] else goto <bb 4>; [90.00%] <bb 3> [local count: 107374184]: a (); <bb 4> [local count: 1073741824]: return 0; } and the reason is that for some reason /* Copy propagation also copy-propagates constants, this is necessary to forward object-size and builtin folding results properly. */ NEXT_PASS (pass_copy_prop); doesn't work: --- a-t2.c.224t.strlen2 2022-11-11 08:44:14.044322291 +0100 +++ a-t2.c.225t.copyprop5 2022-11-11 08:44:14.044322291 +0100 ... <bb 2> [local count: 1073741824]: b_5 = __builtin_object_size (0B, 0); - _1 = 0; - _2 = (long int) _1; + _2 = 0; if (_2 != 0) goto <bb 3>; [10.00%] else I will have a look.
next prev parent reply other threads:[~2022-11-11 7:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-10 15:42 [Bug other/107618] New: " yann at droneaud dot fr 2022-11-10 17:21 ` [Bug middle-end/107618] " yann at droneaud dot fr 2022-11-10 17:45 ` yann at droneaud dot fr 2022-11-11 7:47 ` rguenth at gcc dot gnu.org [this message] 2022-11-11 13:32 ` [Bug tree-optimization/107618] " cvs-commit at gcc dot gnu.org 2022-11-11 13:33 ` rguenth at gcc dot gnu.org 2022-11-11 14:37 ` yann at droneaud dot fr 2022-11-28 22:19 ` pinskia at gcc dot gnu.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-107618-4-JpM5vpkirR@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).