mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Daniel Palmer <daniel@0x0f.com>
Cc: geert@linux-m68k.org, linux-m68k@lists.linux-m68k.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Enable dead code elimination
Date: Tue, 29 Apr 2025 12:18:04 +1000	[thread overview]
Message-ID: <42674c5a-42fe-4846-bf90-340310393fea@linux-m68k.org> (raw)
In-Reply-To: <CAFr9PXmrVUL1HubP04iHR1ObhaNo+mObg7FC+-HpTF7QR0og3g@mail.gmail.com>

Hi Daniel,

On 29/4/25 10:04, Daniel Palmer wrote:
> Hi Greg,
> 
> On Mon, 28 Apr 2025 at 08:37, Greg Ungerer <gerg@linux-m68k.org> wrote:
>> I notice that some other architectures (arm and powerpc) have version
>> checks on gcc or ld in the config. Do you know if there is any version
>> limitations for m68k here?
> 
> I'm not sure about that. I'll try to work out why they have the checks
> and see if that affects m68k too.
> I'm using GCC13 so probably new enough that most things work.

FWIW, the oldest toolchain I had lying around was based on gcc 8.3.0
and binutils 2.32. This patch worked fine on that.

Regards
Greg



  reply	other threads:[~2025-04-29  2:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 11:42 Daniel Palmer
2025-04-27 23:37 ` Greg Ungerer
2025-04-29  0:04   ` Daniel Palmer
2025-04-29  2:18     ` Greg Ungerer [this message]
2025-06-08  8:32       ` Finn Thain
2025-06-08  9:22         ` Finn Thain
2025-06-08  9:36         ` Geert Uytterhoeven
2025-06-11 22:41           ` Daniel Palmer
2025-06-16  4:48 ` Finn Thain
2025-07-06  9:14 ` Geert Uytterhoeven
2025-07-06 10:43   ` Geert Uytterhoeven

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=42674c5a-42fe-4846-bf90-340310393fea@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=daniel@0x0f.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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
all inboxes | Powered by JetHome®