Re: The tale of -mrtd in GCC and Clang

2023-05-10 Thread Richard Z
Hi, very interesting. Somewhere deep in my memory I have the idea that the mrtd option or rtd instruction was designed for Modula 2 which was modern at that time. It was probably pretty useless for a classical K&R c compiler that didn't even understand prototypes until 1989 or so... I assume GC

Re: Question on the m68k Calling Convention (RTD)

2023-04-24 Thread Richard Z
On April 23, 2023 11:15:04 AM UTC, John Paul Adrian Glaubitz wrote: >Now, the interesting part is the question why the compiler is even trying >to take this codepath since RTD should normally be turned off in the M68k >backend by default as it's the case for GCC. > As you say.. looks like t

Re: Using Debian funds to support a gcc development task

2019-09-29 Thread Richard Z
On Sat, Sep 28, 2019 at 11:44:26AM +0200, John Paul Adrian Glaubitz wrote: > As m68k is the oldest port of both the Linux kernel and Debian after i386, > it would be a shame to see it go as there is still very good upstream support > in the Linux kernel with new drivers being added regularly [4],

Re: [parted-devel] Atari label false positives

2018-05-11 Thread Richard Z
On Fri, May 11, 2018 at 06:10:37PM +0200, John Paul Adrian Glaubitz wrote: > According to the documentation, p.43 [1], I think offset $01 should always > contain either "GEM", "BGM" or "XGM". They don't seem to be optional. The Atari partitioning tables are also used on the Q40/Q60 which breaks m

Re: gcc possibly generating invalid assembler

2017-04-17 Thread Richard Z
On Thu, Apr 13, 2017 at 01:08:59PM +0200, John Paul Adrian Glaubitz wrote: > Hi! > > I have unsuccessfully been trying to build liburcu on Debian/m68k. After > adding "m68k" as a detected architecture in configure.ac, the build > fails with the assembler generating syntax error messages [1]: > >

Re: RFC: Support non-standard extension (call via casted function pointer)

2016-01-26 Thread Richard Z
On Mon, Jan 25, 2016 at 10:47:10PM +0100, Michael Karcher wrote: > Hello gcc developers, > > as discussed in https://ghc.haskell.org/trac/ghc/ticket/11395 (and > forwarded as PR c/69221), ghc generates non-compliant C code that is not > compiled as intended on m68k. This is because its internal Cm

Re: previous, a NeXT emulator

2014-12-23 Thread Richard Z
On Mon, Dec 22, 2014 at 11:08:43AM -0800, Zach Brown wrote: > On Mon, Dec 22, 2014 at 09:00:52AM +0100, Geert Uytterhoeven wrote: > > On Mon, Dec 22, 2014 at 7:15 AM, Christian T. Steigies > > wrote: > > > On Sun, Dec 14, 2014 at 07:40:47PM +0100, Geert Uytterhoeven wrote: > > >> On Sun, Dec 14,