public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109230] [13 Regression] Maybe wrong code for opus package on aarch64 since r13-4122-g1bc7efa948f751
Date: Tue, 21 Mar 2023 14:50:17 +0000 [thread overview]
Message-ID: <bug-109230-4-6jCphOkUl6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109230-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109230
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to avieira from comment #3)
> Hi Martin, what options do you build these tests with?
Clicking on the link for the glm package (and then "download logfile") shows
for instance the following (I have not checked whether a certain fine is
compiled differently):
/usr/bin/c++ -I/home/abuild/rpmbuild/BUILD/glm-0.9.9.8
-mbranch-protection=standard -O2
-Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3
-fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables
-fstack-clash-protection -Werror=return-type -flto=auto -g -fPIC
-fno-strict-aliasing -O2 -g -DNDEBUG -O2 -Wno-long-long -MD
next prev parent reply other threads:[~2023-03-21 14:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 11:28 [Bug tree-optimization/109230] New: " marxin at gcc dot gnu.org
2023-03-21 11:38 ` [Bug tree-optimization/109230] " tnfchris at gcc dot gnu.org
2023-03-21 11:41 ` marxin at gcc dot gnu.org
2023-03-21 13:24 ` rguenth at gcc dot gnu.org
2023-03-21 14:46 ` avieira at gcc dot gnu.org
2023-03-21 14:50 ` burnus at gcc dot gnu.org [this message]
2023-03-21 15:29 ` marxin at gcc dot gnu.org
2023-03-21 15:36 ` avieira at gcc dot gnu.org
2023-03-21 15:41 ` marxin at gcc dot gnu.org
2023-03-21 15:45 ` marxin at gcc dot gnu.org
2023-03-21 15:56 ` avieira at gcc dot gnu.org
2023-03-21 15:59 ` jakub at gcc dot gnu.org
2023-03-21 16:02 ` tnfchris at gcc dot gnu.org
2023-03-21 16:05 ` jakub at gcc dot gnu.org
2023-03-21 16:07 ` marxin at gcc dot gnu.org
2023-03-21 16:20 ` jakub at gcc dot gnu.org
2023-03-21 16:23 ` jakub at gcc dot gnu.org
2023-03-21 16:27 ` jakub at gcc dot gnu.org
2023-03-21 19:15 ` jakub at gcc dot gnu.org
2023-03-26 18:18 ` cvs-commit at gcc dot gnu.org
2023-03-26 18:44 ` jakub 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-109230-4-6jCphOkUl6@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).