public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109109] [13 Regression] mariadb fails in tests on i586 (non-LTO mode) after r13-4435-g2c089640279614e3
Date: Tue, 14 Mar 2023 18:27:55 +0000	[thread overview]
Message-ID: <bug-109109-4-LDhAk9YHAp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109109-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #20 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #18)
> Hopefully fixed (the testcase is, but can't verify mariadb).

Thank you for the fix, I'm going to verify the package build.

      parent reply	other threads:[~2023-03-14 18:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 13:53 [Bug tree-optimization/109109] New: " marxin at gcc dot gnu.org
2023-03-13 13:55 ` [Bug target/109109] [13 Regression] " rguenth at gcc dot gnu.org
2023-03-13 13:57 ` marxin at gcc dot gnu.org
2023-03-13 16:43 ` jakub at gcc dot gnu.org
2023-03-13 16:52 ` jakub at gcc dot gnu.org
2023-03-13 21:48 ` marxin at gcc dot gnu.org
2023-03-13 21:50 ` jakub at gcc dot gnu.org
2023-03-13 21:57 ` marxin at gcc dot gnu.org
2023-03-13 21:58 ` marxin at gcc dot gnu.org
2023-03-13 22:01 ` marxin at gcc dot gnu.org
2023-03-13 22:48 ` jakub at gcc dot gnu.org
2023-03-14  7:29 ` marxin at gcc dot gnu.org
2023-03-14  7:30 ` marxin at gcc dot gnu.org
2023-03-14  8:42 ` marxin at gcc dot gnu.org
2023-03-14  9:02 ` jakub at gcc dot gnu.org
2023-03-14 10:11 ` marxin at gcc dot gnu.org
2023-03-14 11:21 ` jakub at gcc dot gnu.org
2023-03-14 11:22 ` marxin at gcc dot gnu.org
2023-03-14 13:46 ` jakub at gcc dot gnu.org
2023-03-14 15:15 ` jakub at gcc dot gnu.org
2023-03-14 18:23 ` jakub at gcc dot gnu.org
2023-03-14 18:26 ` cvs-commit at gcc dot gnu.org
2023-03-14 18:27 ` marxin at gcc dot gnu.org [this message]

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-109109-4-LDhAk9YHAp@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).