public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/97335] [11 Regression] 525.x264_r fails with -Ofast -g -march=znver2 -flto=16 since r11-3641-gc34db4b6f8a5d803
Date: Thu, 08 Oct 2020 12:55:13 +0000 [thread overview]
Message-ID: <bug-97335-4-Ke3aiBINQV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97335-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97335
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
With -O3 -g -flto=16 --param=lto-partitions=1, the first bad binary is with
-fdbg-cnt=ipa_mod_ref:1046.
It seems a misc tool fails with:
./ldecod_r -i BuckBunny.264 -o BuckBunny.yuv
Setting Default Parameters...
Parsing Configfile decoder.cfg
----------------------------- JM 17.1 (FRExt) -----------------------------
--------------------------------------------------------------------------
Input H.264 bitstream : BuckBunny.264
Output decoded YUV : BuckBunny.yuv
Input reference file : test_rec.yuv
--------------------------------------------------------------------------
POC must = frame# or field# for SNRs to be correct
--------------------------------------------------------------------------
Frame POC Pic# QP SnrY SnrU SnrV Y:U:V Time(ms)
--------------------------------------------------------------------------
Input reference file : test_rec.yuv does not exist
SNR values are not available
00000(IDR) 0 0 28 4:2:0 0
00002( P ) 4 1 31 4:2:0 0
00001( b ) 2 2 31 4:2:0 0
00003( I ) 6 2 28 4:2:0 0
00006( P ) 12 4 28 4:2:0 0
mb_qp_delta is out of range
PRE dump files:
https://drive.google.com/file/d/1GzqkYP4PRtXVkVbvGGJUukz8-9ay-uMy/view?usp=sharing
next prev parent reply other threads:[~2020-10-08 12:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 11:54 [Bug ipa/97335] New: " marxin at gcc dot gnu.org
2020-10-08 11:55 ` [Bug ipa/97335] " marxin at gcc dot gnu.org
2020-10-08 12:55 ` marxin at gcc dot gnu.org [this message]
2020-10-08 15:31 ` marxin at gcc dot gnu.org
2020-10-08 15:33 ` marxin at gcc dot gnu.org
2020-10-09 8:27 ` marxin at gcc dot gnu.org
2020-10-09 8:31 ` marxin at gcc dot gnu.org
2020-10-09 8:47 ` marxin at gcc dot gnu.org
2020-10-09 8:48 ` marxin at gcc dot gnu.org
2020-10-09 8:54 ` marxin at gcc dot gnu.org
2020-10-09 9:17 ` marxin at gcc dot gnu.org
2020-10-09 9:25 ` hubicka at gcc dot gnu.org
2020-10-09 10:27 ` cvs-commit at gcc dot gnu.org
2020-10-09 10:28 ` marxin 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-97335-4-Ke3aiBINQV@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: link
Be 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).