public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "admin at levyhsu dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/103997] [12 Regression] gcc.target/i386/pr88531-??.c scan-assembler-times FAILs Date: Tue, 25 Jan 2022 06:01:02 +0000 [thread overview] Message-ID: <bug-103997-4-wrPyTFxNdB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103997-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103997 --- Comment #11 from Levy Hsu <admin at levyhsu dot com> --- Hi Avieira The baseline was one commit before. (ffc7f200adbdf47f14b3594d9b21855c19cf797a) I'm experiencing some issue on local Vtune so I can't say which function or front/backend was affected. objdump shows some different binary, but too long to dig deep. I'll fix the Vtune and see if I can get some results back.
next prev parent reply other threads:[~2022-01-25 6:01 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-12 19:45 [Bug regression/103997] New: " ubizjak at gmail dot com 2022-01-12 19:46 ` [Bug regression/103997] " ubizjak at gmail dot com 2022-01-12 23:13 ` [Bug regression/103997] [12 Regression] " pinskia at gcc dot gnu.org 2022-01-13 3:13 ` crazylht at gmail dot com 2022-01-13 3:27 ` crazylht at gmail dot com 2022-01-13 8:19 ` rguenth at gcc dot gnu.org 2022-01-13 9:17 ` avieira at gcc dot gnu.org 2022-01-13 10:14 ` rguenther at suse dot de 2022-01-13 10:42 ` avieira at gcc dot gnu.org 2022-01-19 14:15 ` cvs-commit at gcc dot gnu.org 2022-01-24 4:00 ` admin at levyhsu dot com 2022-01-24 14:01 ` avieira at gcc dot gnu.org 2022-01-25 6:01 ` admin at levyhsu dot com [this message] 2022-01-25 10:01 ` avieira at gcc dot gnu.org 2022-01-25 11:02 ` rguenth at gcc dot gnu.org 2022-01-26 1:27 ` admin at levyhsu dot com 2022-01-29 22:40 ` write2mark1 2022-01-29 22:50 ` Andrew Pinski
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-103997-4-wrPyTFxNdB@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).