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 lto/104237] [11 Regression] Emitted binary code changes when -g is enabled at -O1 -flto and optimize attribute since r11-3126-ga8f9b4c54cc35062 Date: Tue, 08 Mar 2022 20:48:12 +0000 [thread overview] Message-ID: <bug-104237-4-fBTWXpy2Zv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104237-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104237 --- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The g part of the uuid stands for global revision and the g needs to be removed to get a normal gut hash.
next prev parent reply other threads:[~2022-03-08 20:48 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-26 6:06 [Bug lto/104237] New: Emitted binary code changes when -g is enabled at -O1 -flto tlwang at uwaterloo dot ca 2022-01-26 6:13 ` [Bug lto/104237] Emitted binary code changes when -g is enabled at -O1 -flto and optimize attribute pinskia at gcc dot gnu.org 2022-01-26 8:39 ` [Bug lto/104237] [11/12 Regression] Emitted binary code changes when -g is enabled at -O1 -flto and optimize attribute since r11-3126-ga8f9b4c54cc35062 marxin at gcc dot gnu.org 2022-01-27 14:59 ` jakub at gcc dot gnu.org 2022-01-27 16:26 ` jakub at gcc dot gnu.org 2022-01-27 18:46 ` jakub at gcc dot gnu.org 2022-01-27 18:46 ` jakub at gcc dot gnu.org 2022-01-27 18:58 ` dmalcolm at gcc dot gnu.org 2022-01-28 10:49 ` cvs-commit at gcc dot gnu.org 2022-01-28 10:57 ` [Bug lto/104237] [11 " jakub at gcc dot gnu.org 2022-01-29 6:35 ` cnsun at uwaterloo dot ca 2022-01-29 9:07 ` jakub at gcc dot gnu.org 2022-02-19 8:02 ` cvs-commit at gcc dot gnu.org 2022-02-19 8:06 ` jakub at gcc dot gnu.org 2022-02-23 16:03 ` cnsun at uwaterloo dot ca 2022-03-08 20:34 ` cnsun at uwaterloo dot ca 2022-03-08 20:48 ` pinskia at gcc dot gnu.org [this message] 2022-03-08 20:49 ` jakub at gcc dot gnu.org 2022-03-08 21:07 ` cnsun at uwaterloo dot ca 2022-06-01 15:02 ` cnsun at uwaterloo dot ca 2022-06-01 16:23 ` pinskia at gcc dot gnu.org 2022-06-01 16:42 ` jakub at gcc dot gnu.org 2022-06-01 17:12 ` cnsun at uwaterloo dot ca
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-104237-4-fBTWXpy2Zv@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).