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 debug/103047] Inconsistent arguments ordering for inlined subroutine
Date: Mon, 29 Jan 2024 07:47:22 +0000	[thread overview]
Message-ID: <bug-103047-4-zFniA5tmox@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103047-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:b702dc980215074a06535e3aa52a766bef38af4c

commit r14-8486-gb702dc980215074a06535e3aa52a766bef38af4c
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Jan 26 15:11:47 2024 +0100

    debug/103047 - argument order of inlined functions

    The inliner puts variables for parameters of the inlined functions
    in the inline scope in reverse order.  The following reverses them
    again so that we get consistent ordering between the
    DW_TAG_subprogram DW_TAG_formal_parameter and the
    DW_TAG_inlined_subroutine DW_TAG_formal_parameter set.

    I failed to create a testcase with regexps since the inline
    instances have just abstract origins and so I can't match them up.

            PR debug/103047
            * tree-inline.cc (initialize_inlined_parameters): Reverse
            the decl chain of inlined parameters.

  parent reply	other threads:[~2024-01-29  7:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 14:13 [Bug debug/103047] New: Inconsist " liyd2021 at gmail dot com
2024-01-26 14:07 ` [Bug debug/103047] Inconsistent " rguenth at gcc dot gnu.org
2024-01-29  7:47 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-29  7:47 ` 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-103047-4-zFniA5tmox@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).