public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/105183] New test case gcc.dg/ipa/remref-7.c fails with -m32 Date: Wed, 13 Apr 2022 13:10:04 +0000 [thread overview] Message-ID: <bug-105183-4-jYUu9fOk2O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105183-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105183 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>: https://gcc.gnu.org/g:dd61ee6fde5fcf1d503b679bb9b5e0a0ba7a515d commit r12-8139-gdd61ee6fde5fcf1d503b679bb9b5e0a0ba7a515d Author: Martin Jambor <mjambor@suse.cz> Date: Wed Apr 13 15:08:59 2022 +0200 testsuite: Increase auto-inlining param in gcc.dg/ipa/remref-7.c (PR 105183) A scan dump of testsuite gcc.dg/ipa/remref-7.c fails on a number of platforms. I investigated only i?86-*-* with -mno-sse but assume the issue is the same on all of the affected platform. Because function bar is not inlined there even though it is only called once, the process that is being tested is simply not triggered. This can be "fixed" by increasing parameter max-inline-insns-auto to something high, I randomly picked 100. I have only manually tested the change but hopefully that is enough. gcc/testsuite/ChangeLog: 2022-04-08 Martin Jambor <mjambor@suse.cz> PR testsuite/105183 * gcc.dg/ipa/remref-7.c: Add --param max-inline-insns-auto=100 to options.
next prev parent reply other threads:[~2022-04-13 13:10 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-06 18:18 [Bug other/105183] New: " seurer at gcc dot gnu.org 2022-04-07 7:09 ` [Bug testsuite/105183] " rguenth at gcc dot gnu.org 2022-04-07 21:43 ` hp at gcc dot gnu.org 2022-04-08 9:39 ` jamborm at gcc dot gnu.org 2022-04-08 10:13 ` jamborm at gcc dot gnu.org 2022-04-08 10:59 ` jamborm at gcc dot gnu.org 2022-04-13 13:10 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-13 13:10 ` jamborm 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-105183-4-jYUu9fOk2O@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).