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 debug/104407] [10/11/12 Regression] '-fcompare-debug' failure (length) w/ -std=c++17 -O1
Date: Mon, 07 Feb 2022 10:50:28 +0000	[thread overview]
Message-ID: <bug-104407-4-UNyvuJXD7Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104407-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104407

--- Comment #13 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #12)
> Created attachment 52362 [details]
> gcc12-pr104407.patch
> 
> This works for me.

Yes.  Note we're throwing away the result anyway but the comment at the caller
hints at the expansion being necessary because that triggers mangling.  Now,
with your change we won't ever do any mangling and thus we can instead avoid
calling the function at all?

  parent reply	other threads:[~2022-02-07 10:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-06  7:32 [Bug debug/104407] New: " asolokha at gmx dot com
2022-02-06  8:51 ` [Bug debug/104407] " pinskia at gcc dot gnu.org
2022-02-06  8:52 ` [Bug target/104407] " pinskia at gcc dot gnu.org
2022-02-07  9:05 ` jakub at gcc dot gnu.org
2022-02-07  9:17 ` jakub at gcc dot gnu.org
2022-02-07  9:19 ` jakub at gcc dot gnu.org
2022-02-07  9:23 ` jakub at gcc dot gnu.org
2022-02-07  9:31 ` rguenth at gcc dot gnu.org
2022-02-07  9:38 ` jakub at gcc dot gnu.org
2022-02-07  9:42 ` jakub at gcc dot gnu.org
2022-02-07  9:42 ` rguenth at gcc dot gnu.org
2022-02-07  9:44 ` rguenth at gcc dot gnu.org
2022-02-07  9:50 ` [Bug debug/104407] " jakub at gcc dot gnu.org
2022-02-07 10:50 ` rguenth at gcc dot gnu.org [this message]
2022-02-07 11:10 ` jakub at gcc dot gnu.org
2022-02-07 11:22 ` rguenther at suse dot de
2022-02-07 11:35 ` jakub at gcc dot gnu.org
2022-02-09 14:19 ` cvs-commit at gcc dot gnu.org
2022-02-09 14:19 ` [Bug debug/104407] [10/11 " jakub at gcc dot gnu.org
2022-06-28 10:48 ` jakub at gcc dot gnu.org
2023-07-07 10:42 ` [Bug debug/104407] [11 " rguenth 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-104407-4-UNyvuJXD7Y@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).