public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/93242] [MIPS] patchable-function-entry broken
       [not found] <bug-93242-4@http.gcc.gnu.org/bugzilla/>
@ 2022-09-01  9:00 ` iii at linux dot ibm.com
  2022-09-01 11:47 ` mikpelinux at gmail dot com
  2022-09-01 12:20 ` iii at linux dot ibm.com
  2 siblings, 0 replies; 3+ messages in thread
From: iii at linux dot ibm.com @ 2022-09-01  9:00 UTC (permalink / raw)
  To: gcc-bugs

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

Ilya Leoshkevich <iii at linux dot ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |iii at linux dot ibm.com

--- Comment #9 from Ilya Leoshkevich <iii at linux dot ibm.com> ---
Would it be possible to backport this to gcc-9?

Linux kernel will start using patchable_function_entry soon, and there are
problems with s390x, which this patch fixes as well:
https://lore.kernel.org/bpf/9099057e-124c-8f30-c29d-54be85eeebfd@iogearbox.net/

There is a workaround for now, but it would be good to have this fixed in all
the maintained gccs (gcc-8 is no longer maintained as far as I can see, so this
leaves only gcc-9).

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug target/93242] [MIPS] patchable-function-entry broken
       [not found] <bug-93242-4@http.gcc.gnu.org/bugzilla/>
  2022-09-01  9:00 ` [Bug target/93242] [MIPS] patchable-function-entry broken iii at linux dot ibm.com
@ 2022-09-01 11:47 ` mikpelinux at gmail dot com
  2022-09-01 12:20 ` iii at linux dot ibm.com
  2 siblings, 0 replies; 3+ messages in thread
From: mikpelinux at gmail dot com @ 2022-09-01 11:47 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #10 from Mikael Pettersson <mikpelinux at gmail dot com> ---
(In reply to Ilya Leoshkevich from comment #9)
> Would it be possible to backport this to gcc-9?
...
> There is a workaround for now, but it would be good to have this fixed in
> all the maintained gccs (gcc-8 is no longer maintained as far as I can see,
> so this leaves only gcc-9).

GCC-9 went EOL with the gcc-9.5.0 release on May 27 this year.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug target/93242] [MIPS] patchable-function-entry broken
       [not found] <bug-93242-4@http.gcc.gnu.org/bugzilla/>
  2022-09-01  9:00 ` [Bug target/93242] [MIPS] patchable-function-entry broken iii at linux dot ibm.com
  2022-09-01 11:47 ` mikpelinux at gmail dot com
@ 2022-09-01 12:20 ` iii at linux dot ibm.com
  2 siblings, 0 replies; 3+ messages in thread
From: iii at linux dot ibm.com @ 2022-09-01 12:20 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #11 from Ilya Leoshkevich <iii at linux dot ibm.com> ---
I see.  It would be good to update https://gcc.gnu.org/gcc-9/ then - e.g.
https://gcc.gnu.org/gcc-8/ says "This release series is no longer supported".

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-09-01 12:20 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-93242-4@http.gcc.gnu.org/bugzilla/>
2022-09-01  9:00 ` [Bug target/93242] [MIPS] patchable-function-entry broken iii at linux dot ibm.com
2022-09-01 11:47 ` mikpelinux at gmail dot com
2022-09-01 12:20 ` iii at linux dot ibm.com

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).