From: Fredrik Noring <noring@nocrew.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Alexander Monakov <amonakov@ispras.ru>, gcc-help@gcc.gnu.org
Subject: Re: m68k: Simple loop compiles into boundless recursion with -O2
Date: Wed, 13 Jan 2021 20:53:13 +0100 [thread overview]
Message-ID: <X/9PqXjpM4SttWJZ@sx9> (raw)
In-Reply-To: <20210113192015.GT30983@gate.crashing.org>
Hi Segher,
> Yup, always always always use -dr :-)
Noted!
> You probably want -ffreestanding anyway for your situation: -nostdlib
> does not mean "there is no standard library", it just means "do not link
> with it".
Ah, yes.
> For the archives, no one has said it yet: to just disable the
> optimisation transforming the loop into a memset, you can use
> -fno-tree-loop-distribute-patterns .
It's a new 32-bit libc (for Atari TOS), and maximum GCC optimisations are
welcome, although I haven't yet figured out exactly where the boundary is
between the GCC built-ins and this libc implementation. There is obviously
some overlap between the two, and I wouldn't want the libc to stand in the
way of GCC's optimisations.
Other than that things work quite well so far, compiling programs, etc.
It was surprisingly simple and straight-forward, but then of course this
vintage 1985 operating system isn't complicated either. :)
[ The name TOS/libc is provisional, it will be renamed to Fuji/libc shortly. ]
Fredrik
next prev parent reply other threads:[~2021-01-13 19:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 16:01 Fredrik Noring
2021-01-13 16:09 ` Alexander Monakov
2021-01-13 16:30 ` Fredrik Noring
2021-01-13 19:20 ` Segher Boessenkool
2021-01-13 19:53 ` Fredrik Noring [this message]
2021-01-13 21:46 ` Segher Boessenkool
2021-01-13 21:54 ` AW: " Stefan Franke
2021-01-14 14:54 ` Fredrik Noring
2021-01-14 15:05 ` Alexander Monakov
2021-01-14 15:09 ` Alexander Monakov
2021-01-14 15:15 ` AW: " Stefan Franke
2021-01-14 15:33 ` Alexander Monakov
2021-01-14 15:56 ` AW: " Stefan Franke
2021-01-15 2:23 ` Liu Hao
2021-01-15 6:23 ` Fredrik Noring
2021-01-13 16:23 ` AW: " Stefan Franke
2021-01-13 17:27 ` Fredrik Noring
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=X/9PqXjpM4SttWJZ@sx9 \
--to=noring@nocrew.org \
--cc=amonakov@ispras.ru \
--cc=gcc-help@gcc.gnu.org \
--cc=segher@kernel.crashing.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).