public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sbergman at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106355] Linux s390x -O2 argument passing miscompile
Date: Wed, 20 Jul 2022 08:14:24 +0000	[thread overview]
Message-ID: <bug-106355-4-UdNBN1QgLG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106355-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Stephan Bergmann <sbergman at redhat dot com> ---
(In reply to Richard Biener from comment #1)
> Did you see whether this is changed behavior from GCC 11?

I didn't check that myself, but the Debian LibreOffice maintainer claims that
he sees the same symptoms when building with some GCC 11 (against some GCC 12
libstdc++, though).  (It appears that this issue only happened to start to hit
builds of LibreOffice after some recent code changes in LibreOffice, so we
don't have any historic data on which versions of GCC would not have had this
issue.)

  parent reply	other threads:[~2022-07-20  8:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 14:28 [Bug other/106355] New: " sbergman at redhat dot com
2022-07-20  8:06 ` [Bug target/106355] " rguenth at gcc dot gnu.org
2022-07-20  8:14 ` sbergman at redhat dot com [this message]
2022-08-15 13:00 ` dan at danny dot cz
2022-08-15 13:20 ` stefansf at linux dot ibm.com
2022-10-19 12:29 ` cvs-commit at gcc dot gnu.org
2022-10-25  8:35 ` cvs-commit at gcc dot gnu.org
2022-10-25  8:37 ` cvs-commit at gcc dot gnu.org
2022-10-25  8:39 ` cvs-commit at gcc dot gnu.org
2024-02-29 20:19 ` mpolacek 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-106355-4-UdNBN1QgLG@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).