public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug compile/31397] arrays with structs with arrays gets the wrong alignment Date: Thu, 29 Feb 2024 22:38:05 +0000 [thread overview] Message-ID: <bug-31397-4717-SBB8uF4DYM@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31397-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31397 --- Comment #5 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f9771d0e80c3a98e865c7ee5139cadf9d73db436 commit f9771d0e80c3a98e865c7ee5139cadf9d73db436 Author: Tom Tromey <tom@tromey.com> Date: Tue Feb 20 17:15:03 2024 -0700 Synchronize GCC compile plugin headers This patch copies some changes to the compile headers from GCC's include/ directory. It is the gdb equivalent of the GCC commit bc0e18a9 -- however, while that commit also necessarily touched libcc1, this one of course does not. Tested by rebuilding and also running the gdb.compile tests. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31397 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-29 22:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-18 2:57 [Bug compile/31397] New: " pinskia at gcc dot gnu.org 2024-02-18 2:57 ` [Bug compile/31397] " pinskia at gcc dot gnu.org 2024-02-18 3:01 ` pinskia at gcc dot gnu.org 2024-02-18 6:59 ` sam at gentoo dot org 2024-02-18 10:23 ` ssbssa at sourceware dot org 2024-02-20 18:25 ` tromey at sourceware dot org 2024-02-22 1:46 ` tromey at sourceware dot org 2024-02-29 22:38 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-14 15:56 ` cvs-commit at gcc dot gnu.org 2024-03-14 15:56 ` tromey at sourceware dot 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-31397-4717-SBB8uF4DYM@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).