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 libcc1/113977] debug info for alignment of structure is unspecified Date: Thu, 29 Feb 2024 16:08:02 +0000 [thread overview] Message-ID: <bug-113977-4-vHkCOrBygf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113977-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113977 --- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@gcc.gnu.org>: https://gcc.gnu.org/g:bc0e18a960f9dff3e740f4d0cb5b25b3f68d920a commit r14-9239-gbc0e18a960f9dff3e740f4d0cb5b25b3f68d920a Author: Tom Tromey <tom@tromey.com> Date: Mon Feb 26 18:21:03 2024 -0700 Fix PR libcc1/113977 PR libcc1/113977 points out a case where a simple expression is rejected with a compiler error message. The bug here is that gdb does not inform the plugin of the correct alignment -- in fact, there is no way to do that. This patch adds a new method to allow the alignment to be set, and bumps the C front end protocol version. It also includes some updates to various comments in 'include', done here to simplify the merge to binutils-gdb. include * gcc-cp-interface.h (gcc_cp_fe_context_function): Update comment. * gcc-c-interface.h (enum gcc_c_api_version) <GCC_C_FE_VERSION_2>: New constant. (gcc_c_fe_context_function): Update comment. * gcc-c-fe.def (finish_record_with_alignment): New method. Update documentation. libcc1 PR libcc1/113977 * libcc1plugin.cc (plugin_finish_record_or_union): New function. (plugin_finish_record_or_union): Rewrite. (plugin_init): Use GCC_C_FE_VERSION_2. * libcc1.cc (c_vtable): Use GCC_C_FE_VERSION_2. (gcc_c_fe_context): Check for GCC_C_FE_VERSION_2.
next prev parent reply other threads:[~2024-02-29 16:08 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-18 2:06 [Bug debug/113977] New: " tsqurt at outlook dot com 2024-02-18 2:29 ` [Bug debug/113977] " pinskia at gcc dot gnu.org 2024-02-18 2:32 ` [Bug libcc1/113977] " pinskia at gcc dot gnu.org 2024-02-18 2:35 ` pinskia at gcc dot gnu.org 2024-02-18 2:41 ` tsqurt at outlook dot com 2024-02-18 2:47 ` pinskia at gcc dot gnu.org 2024-02-18 2:48 ` pinskia at gcc dot gnu.org 2024-02-18 2:58 ` pinskia at gcc dot gnu.org 2024-02-18 3:06 ` pinskia at gcc dot gnu.org 2024-02-20 18:27 ` tromey at gcc dot gnu.org 2024-02-20 18:32 ` pinskia at gcc dot gnu.org 2024-02-22 1:46 ` tromey at gcc dot gnu.org 2024-02-29 16:08 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-29 16:34 ` tromey at gcc dot gnu.org 2024-03-07 8:20 ` pinskia 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-113977-4-vHkCOrBygf@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).