public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libobjc/109913] [14 regression] r14-976-g9907413a3a6aa3 causes more than 300 objc/objc++ failures
Date: Sun, 21 May 2023 16:32:40 +0000	[thread overview]
Message-ID: <bug-109913-4-9mh8nadOSu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109913-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Iain Sandoe <iains at gcc dot gnu.org> ---
I'd think that the simple local fix would be reaosnable for now
 - Andrew has noted on IRC that we really should have a better way to get the
target-specific info

(better than replicating the logic for each target that needs it; likely
imcompletely, certainly w.r.t any user-defined alignment changes)

  parent reply	other threads:[~2023-05-21 16:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 21:06 [Bug objc/109913] New: " seurer at gcc dot gnu.org
2023-05-19 22:36 ` [Bug objc/109913] " pinskia at gcc dot gnu.org
2023-05-19 22:39 ` pinskia at gcc dot gnu.org
2023-05-19 22:40 ` pinskia at gcc dot gnu.org
2023-05-19 23:06 ` pinskia at gcc dot gnu.org
2023-05-20 23:25 ` [Bug libobjc/109913] " rep.dot.nop at gmail dot com
2023-05-20 23:27 ` pinskia at gcc dot gnu.org
2023-05-20 23:41 ` rep.dot.nop at gmail dot com
2023-05-21 16:30 ` iains at gcc dot gnu.org
2023-05-21 16:32 ` iains at gcc dot gnu.org [this message]
2023-05-22 13:52 ` iains at gcc dot gnu.org
2023-05-22 14:19 ` pinskia at gcc dot gnu.org
2023-05-22 21:43 ` cvs-commit at gcc dot gnu.org
2023-05-27  5:52 ` 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-109913-4-9mh8nadOSu@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).