On Sat, 26 Oct 2024, Andreas Schwab wrote:
>Already basic things like struct stat64 will break.
OK. Then, flag day, I guess.
How do we model this in Debian. Rename libc to libc6.1 and
conflict with libc6 to force no coïnstallability, rename the
architecture from m68k to… something else, or…?
Bu
On Okt 25 2024, Thorsten Glaser wrote:
> Question is, do we need a kernel change for this at all?
> Is there anything in the kernel/userland interface that
> gets affected by this, or do these APIs use sufficient
> explicit padding? Has anyone looked at this?
Already basic things like struct stat
On Fri, 25 Oct 2024, John Paul Adrian Glaubitz wrote:
>as m68k has supported 32-bit alignment through the "-malign-int"
>switch for a long time.
That switch constitutes a fundamental ABI change, even if
the effect is limited.
Question is, do we need a kernel change for this at all?
Is there anyt
On Okt 25 2024, Arnd Bergmann wrote:
> Doing it without a migration path seems worse to me,
> as this would mean breaking every single existing
> installation between two kernels, and making it impossible
> to bisect other issues, and breaking the rule #1.
That's why I didn't change the alignment
On Fri, Oct 25, 2024, at 10:10, John Paul Adrian Glaubitz wrote:
> On Fri, 2024-10-25 at 09:55 +, Arnd Bergmann wrote:
>> I think the idea of using the generic syscall ABI (in particular
>> the time64-only variant) makes sense if there is going to be a
>> new ABI, and I can help figure out what
On Fri, Oct 25, 2024, at 06:48, John Paul Adrian Glaubitz wrote:
> Hello,
>
> the m68k port has reached the point where switching the default alignment
> from 16-bit to 32-bit is inevitable as the number of packages affected by
> alignment issues have become too large. It even includes Python 3.13
Hi Arnd,
On Fri, 2024-10-25 at 09:55 +, Arnd Bergmann wrote:
> I think the idea of using the generic syscall ABI (in particular
> the time64-only variant) makes sense if there is going to be a
> new ABI, and I can help figure out what needs to be done in the
> kernel for that.
I don't actuall
On Fri, 25 Oct 2024, John Paul Adrian Glaubitz wrote:
> the m68k port has reached the point where switching the default
> alignment from 16-bit to 32-bit is inevitable as the number of packages
> affected by alignment issues have become too large. It even includes
> Python 3.13 these days.
>
On Fri, 2024-10-25 at 20:06 +1100, Finn Thain wrote:
> On Fri, 25 Oct 2024, John Paul Adrian Glaubitz wrote:
>
> > the m68k port has reached the point where switching the default
> > alignment from 16-bit to 32-bit is inevitable as the number of packages
> > affected by alignment issues have bec
9 matches
Mail list logo
