public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rin at NetBSD dot 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 03:36:23 +0000	[thread overview]
Message-ID: <bug-101469-4-whFpFIx4GY@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 #10 from Rin Okuyama <rin at NetBSD dot org> ---
(In reply to Oleg Endo from comment #9)
> Sorry for being late for 2 years with this.
...
> 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.

No problem at all! We will probably ship GCC 10.5 with your fix for NetBSD 10.
And we will switch to GCC 12 for NetBSD-current soon.

> I will commit the patch to all open GCC versions.

I'm looking forward to it :)

I'm really excited to know that we have active GCC developer working on SH!

Thanks,
rin

  parent reply	other threads:[~2023-07-10  3:36 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
2023-07-10  3:36 ` rin at NetBSD dot org [this message]
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-whFpFIx4GY@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).