From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Rob Landley <rob@landley.net>, Finn Thain <fthain@telegraphics.com.au>
Cc: linux-m68k@vger.kernel.org, Laurent Vivier <Laurent@Vivier.EU>
Subject: Re: GCC?, was Re: Running m68k on qemu with external initramfs?
Date: Mon, 13 Apr 2020 09:41:07 +0200 [thread overview]
Message-ID: <78fbcc17-4b66-bf43-13fe-15b18effa86d@physik.fu-berlin.de> (raw)
In-Reply-To: <eb942a46-515f-9e1e-eeab-22c50b56e07c@landley.net>
On 4/13/20 9:07 AM, Rob Landley wrote:
> It was. -O2 still segfaults the same way, but -O1 runs fine.
> (...)
> Did I mention I'm really done with gcc development ever since they decided to
> rewrite everything in C++? Sigh. [grind grind grind...]
>
> CFLAGS='-fgcse'
>
> That's the one.
You should try gcc-10 where the m68k backend has seen a large overhaul.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2020-04-13 7:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 0:50 Running m68k on qemu with external initramfs? Rob Landley
2020-04-11 6:12 ` Finn Thain
2020-04-12 3:36 ` Rob Landley
2020-04-12 5:29 ` Finn Thain
2020-04-12 12:34 ` Rob Landley
2020-04-12 8:27 ` John Paul Adrian Glaubitz
2020-04-12 8:31 ` Laurent Vivier
2020-04-12 21:48 ` Rob Landley
2020-04-12 23:17 ` Finn Thain
2020-04-11 12:12 ` John Paul Adrian Glaubitz
2020-04-12 12:48 ` Rob Landley
2020-04-12 13:02 ` John Paul Adrian Glaubitz
2020-04-12 21:56 ` Rob Landley
2020-04-12 23:30 ` GCC?, was " Finn Thain
2020-04-13 0:28 ` Rob Landley
2020-04-13 5:17 ` Finn Thain
2020-04-13 7:07 ` Rob Landley
2020-04-13 7:41 ` John Paul Adrian Glaubitz [this message]
2020-04-13 8:27 ` Rob Landley
2020-04-13 9:42 ` Geert Uytterhoeven
2020-04-13 23:02 ` 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=78fbcc17-4b66-bf43-13fe-15b18effa86d@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=Laurent@Vivier.EU \
--cc=fthain@telegraphics.com.au \
--cc=linux-m68k@vger.kernel.org \
--cc=rob@landley.net \
/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 NNTP newsgroup(s).