All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: John Paul Adrian Glaubitz via Libc-help <libc-help@sourceware.org>
Cc: James Le Cuirot <chewi@aura-online.co.uk>,
	 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	 debian-68k <debian-68k@lists.debian.org>,
	linux-m68k <linux-m68k@vger.kernel.org>
Subject: Re: Tuple and changes for m68k with -malign-int
Date: Mon, 19 May 2025 10:14:04 +0200	[thread overview]
Message-ID: <8734d1kofn.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <08ce465732a0eb0dce550978c98ef822abba5f96.camel@physik.fu-berlin.de> (John Paul Adrian Glaubitz via Libc-help's message of "Sun, 18 May 2025 09:09:19 +0200")

* John Paul Adrian Glaubitz via Libc-help:

> I was just looking at the necessary changes to switch m68k to 32-bit alignment
> and I'm not sure we need to do anything about glibc. I am documenting my current
> findings here [1].

>> [1] https://wiki.debian.org/M68k/Alignment

Why doesn't this change need a new target triple?  This change alters
struct layout (it introduces new padding in some cases), so it's quite
incompatible with what we have today.

Thanks,
Florian


  parent reply	other threads:[~2025-05-19  8:14 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e9035006d50933fb02727fa373629cc821784f6c.camel@aura-online.co.uk>
2023-08-26 10:51 ` Tuple and changes for m68k with -malign-int John Paul Adrian Glaubitz
2023-08-26 19:24   ` Richard
2023-08-26 20:43     ` James Le Cuirot
2023-08-28  6:54       ` Geert Uytterhoeven
2023-08-28 10:57     ` John Paul Adrian Glaubitz
2023-08-28 12:11       ` Richard
2023-08-28 12:22         ` Geert Uytterhoeven
2023-08-28 12:46         ` John Paul Adrian Glaubitz
2023-08-27  0:46   ` Finn Thain
2023-08-27  9:20     ` James Le Cuirot
2023-08-27 11:27       ` Richard
2023-08-28  7:00       ` Geert Uytterhoeven
2023-08-28 11:26         ` Richard
2023-08-28 11:40           ` Geert Uytterhoeven
2023-08-28 20:16           ` Richard
2023-08-29  6:52             ` Geert Uytterhoeven
2023-08-28  6:56     ` Geert Uytterhoeven
2023-08-28 11:13       ` John Paul Adrian Glaubitz
2023-08-29  1:12         ` Finn Thain
2023-08-28 11:10     ` John Paul Adrian Glaubitz
2023-08-28 12:44       ` Adhemerval Zanella Netto
2023-08-28 12:50         ` John Paul Adrian Glaubitz
2023-08-28 13:17           ` Andreas Schwab
2023-08-29 10:51             ` John Paul Adrian Glaubitz
2023-08-29 15:27               ` Geert Uytterhoeven
2023-08-28 13:29           ` James Le Cuirot
2023-08-29 10:54             ` John Paul Adrian Glaubitz
2023-08-29 21:53               ` Karoly Balogh
2023-08-30  1:33                 ` Jeffrey Walton
2023-08-29  1:14       ` Finn Thain
2023-08-29  8:52         ` Eero Tamminen
2024-05-15 17:08   ` Python requires 32-bit alignment now - was: " John Paul Adrian Glaubitz
2025-05-18  7:09 ` John Paul Adrian Glaubitz
2025-05-18 14:39   ` Antonio Vargas Gonzalez
2025-05-18 15:07     ` John Paul Adrian Glaubitz
2025-05-19  7:42       ` Geert Uytterhoeven
2025-05-19  7:54         ` John Paul Adrian Glaubitz
2025-05-19  8:03           ` Andreas Schwab
2025-05-19  8:18             ` John Paul Adrian Glaubitz
2025-05-19  8:25               ` Geert Uytterhoeven
2025-05-19  8:43                 ` John Paul Adrian Glaubitz
2025-05-19  8:07           ` Geert Uytterhoeven
2025-05-19  8:14   ` Florian Weimer [this message]
2025-05-19  8:24     ` John Paul Adrian Glaubitz
2025-05-19 21:51       ` James Le Cuirot
2025-05-20  9:39         ` John Paul Adrian Glaubitz
2025-05-21  9:15           ` James Le Cuirot
2025-05-21  9:19             ` John Paul Adrian Glaubitz
2025-05-19 21:59       ` Finn Thain
2025-05-20  7:55         ` John Paul Adrian Glaubitz
2025-05-20  8:24           ` Geert Uytterhoeven
2025-05-20  8:37             ` John Paul Adrian Glaubitz
2025-05-20  9:46               ` Finn Thain
2025-05-20  9:56                 ` John Paul Adrian Glaubitz
2025-05-20  9:58               ` Geert Uytterhoeven
2025-05-20 10:05                 ` John Paul Adrian Glaubitz
2025-05-20 10:09                   ` Geert Uytterhoeven
2025-05-20 10:12                     ` John Paul Adrian Glaubitz
2025-05-20 22:13                 ` John Paul Adrian Glaubitz
2025-05-21  0:29               ` Finn Thain
2025-05-21  1:59                 ` John Klos
2025-05-21  5:18                   ` Finn Thain
2025-05-26  5:25                     ` Finn Thain
2025-05-21  7:28                   ` Finn Thain
2025-05-21  9:56                   ` John Paul Adrian Glaubitz
2025-05-21 14:09                   ` Debian subset suitable for m68k (was: Tuple and changes for m68k with -malign-int) Eero Tamminen
2025-05-21 17:54                     ` John Paul Adrian Glaubitz
2025-05-21 22:14                       ` Eero Tamminen
2025-06-17  7:02                   ` Tuple and changes for m68k with -malign-int Geert Uytterhoeven
2025-06-17  7:25                     ` John Paul Adrian Glaubitz
2025-06-17  7:40                       ` Geert Uytterhoeven
2025-06-17  9:48                         ` John Paul Adrian Glaubitz
2025-06-17  9:59                           ` Geert Uytterhoeven
2025-06-17 10:13                             ` John Paul Adrian Glaubitz
2025-06-17 11:21                               ` Geert Uytterhoeven
2025-06-17 11:37                                 ` John Paul Adrian Glaubitz
2025-05-20  9:39           ` Finn Thain
2025-05-20  9:43             ` John Paul Adrian Glaubitz
2025-05-20  9:55               ` Finn Thain
2025-05-20 10:18                 ` John Paul Adrian Glaubitz
2025-05-20 11:03                   ` Finn Thain
2025-05-20 11:13                     ` John Paul Adrian Glaubitz
2025-05-21  0:14                       ` Finn Thain
2025-05-21 17:36 John Klos
2025-05-21 23:50 ` Finn Thain

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=8734d1kofn.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=chewi@aura-online.co.uk \
    --cc=debian-68k@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=libc-help@sourceware.org \
    --cc=linux-m68k@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.