public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: <stefan@franke.ms>
To: <gcc-help@gcc.gnu.org>
Subject: AW: AW: autoinc / postinc not used
Date: Thu, 18 Jan 2024 17:17:05 +0100	[thread overview]
Message-ID: <005801da4a29$c76dfe40$5649fac0$@franke.ms> (raw)
In-Reply-To: <58bef82f4a7de6493aa9c6482ad519d3089b9ebe.camel@t-online.de>

> -----Ursprüngliche Nachricht-----
> Von: Gcc-help <gcc-help-bounces+bebbo=bejy.net@gcc.gnu.org> Im Auftrag
> von Oleg Endo
> Gesendet: Donnerstag, 18. Januar 2024 00:33
> An: stefan@franke.ms; gcc-help@gcc.gnu.org
> Betreff: Re: AW: autoinc / postinc not used
> 
> 
> On Wed, 2024-01-17 at 16:19 +0100, stefan@franke.ms wrote:
> >
> >
> > There are some more hacks needed to fix the handling here and there, most
> work is needed for -funroll-loops. After all, gcc creates beautiful code as
> shown here http://franke.ms/cex/z/MGTb5P . There it's still the old version
> 6.5.0, but maybe I'll port that to a more recent version.
> > If there is interest for other targets, I can provide the information to apply
> my changes. Or you grab it yourself from my github repo.
> >
> >
> 
> The results you're getting on GCC 6 look great.  Where is the patch or your
> github repo?
> 
> Cheers,
> Oleg

My gcc repo is here: https://github.com/bebbo/gcc and the most important branch is amiga6. Some changes are inside ifdef blocks with TARGET_M68K or TARGET_AMIGAOS. So don't expect to benefits out of the box...
... 

Regards

Stefan


  reply	other threads:[~2024-01-18 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 20:02 stefan
2024-01-16 23:52 ` Oleg Endo
2024-01-17 15:19   ` AW: " stefan
2024-01-17 23:32     ` Oleg Endo
2024-01-18 16:17       ` stefan [this message]
2024-01-30 12:22         ` AW: " Oleg Endo

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='005801da4a29$c76dfe40$5649fac0$@franke.ms' \
    --to=stefan@franke.ms \
    --cc=gcc-help@gcc.gnu.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).