public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101469] wrong code with "-O2 -fPIE" for SH
Date: Mon, 10 Jul 2023 02:45:16 +0000	[thread overview]
Message-ID: <bug-101469-4-aRTX5Bc3oz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101469-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101469

--- Comment #9 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to Rin Okuyama from comment #8)
> (In reply to Oleg Endo from comment #7)
> 
> Hi Oleg. Thank you very much for your great work!
> 
> I've tested your patch with GCC 10.4.0 in this weekend, and it perfectly
> worked:
> - testcase attached to comment #0 compiled correctly
> - full regression tests on NetBSD/shle-current built by patched GCC
> successfully completed without any regression (compared with system built by
> GCC with that peephole optimization removed)
> - some 3rd party softwares (including perl 5.36.0, ruby 3.10.10, zsh 5.9,
> ...) self-built on shle host by GCC of same code base
> 
> Let me thank you again, Oleg!
> 
> rin

Thanks you so much for getting back!  Sorry for being late for 2 years with
this.  I will commit the patch to all open GCC versions.  Unfortunately GCC
10.5 has just been released recently and that was the last version 10.  So the
patch will be included from GCC version 11.

  parent reply	other threads:[~2023-07-10  2:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16  9:48 [Bug c/101469] New: " rin at NetBSD dot org
2021-07-18  4:18 ` [Bug target/101469] " rin at NetBSD dot org
2021-07-18 17:04 ` uwe at netbsd dot org
2021-07-19  5:23 ` rin at NetBSD dot org
2021-07-19  5:55 ` olegendo at gcc dot gnu.org
2021-07-19  6:13 ` rin at NetBSD dot org
2021-07-21 16:40 ` rin at NetBSD dot org
2023-07-07 10:25 ` olegendo at gcc dot gnu.org
2023-07-07 10:28 ` olegendo at gcc dot gnu.org
2023-07-10  2:39 ` rin at NetBSD dot org
2023-07-10  2:45 ` olegendo at gcc dot gnu.org [this message]
2023-07-10  3:36 ` rin at NetBSD dot org
2023-07-14  1:40 ` cvs-commit at gcc dot gnu.org
2023-07-14  1:45 ` cvs-commit at gcc dot gnu.org
2023-07-14  1:51 ` cvs-commit at gcc dot gnu.org
2023-07-14  2:03 ` cvs-commit at gcc dot gnu.org
2023-07-14  2:10 ` olegendo at gcc dot gnu.org
2023-07-18  3:57 ` rin at NetBSD dot org
2023-07-18  4:05 ` olegendo at gcc dot gnu.org

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=bug-101469-4-aRTX5Bc3oz@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).