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 plugins/108634] [13 regression] 'undefined symbol: tree_code_type' when building kernel GCC plugins since r13-5431-gb0241ce6e37031
Date: Fri, 17 Mar 2023 07:45:22 +0000	[thread overview]
Message-ID: <bug-108634-4-BEK7tgTiuD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108634-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

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

commit r13-6730-gbe6195c7e7adc7465214a0dc347c592822713c3f
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Mar 17 08:44:19 2023 +0100

    gdbhooks: Update gdbhooks.py for recent tree_code_type changes [PR108634]

    On Mon, Mar 13, 2023 at 04:15:12PM -0400, Jason Merrill wrote:
    > The r13-6577 change to use tree_code_type_tmpl in earlier C++ dialects
broke
    > gdbhooks, which expects tree_code_type to always be available.  I
considered
    > trying to make gdbhooks more robust, but it seemed simpler to define
    > tree_code_type as a reference to the template.

    As I said earlier, I think it is better to tweak gdbhooks.

    The following patch does that, I've tested it now both with gcc 12 and
    older gcc as system compiler and the patch fixed the latter while keeping
    the former working as before.

    2023-03-17  Jakub Jelinek  <jakub@redhat.com>

            PR plugins/108634
            * gdbhooks.py (TreePrinter.to_string): Wrap
            gdb.parse_and_eval('tree_code_type') in a try block, parse
            and eval 'tree_code_type_tmpl<0>::tree_code_type' instead if it
            raises exception.  Update comments for the recent tree_code_type
            changes.

      parent reply	other threads:[~2023-03-17  7:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 22:37 [Bug plugins/108634] New: " sam at gentoo dot org
2023-02-01 22:44 ` [Bug plugins/108634] " arsen at aarsen dot me
2023-02-01 22:46 ` sam at gentoo dot org
2023-02-01 22:48 ` pinskia at gcc dot gnu.org
2023-02-01 23:11 ` sam at gentoo dot org
2023-02-04  0:09 ` jakub at gcc dot gnu.org
2023-03-10  9:40 ` cvs-commit at gcc dot gnu.org
2023-03-17  7:45 ` cvs-commit at gcc dot gnu.org [this message]

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-108634-4-BEK7tgTiuD@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).