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 tree-optimization/104263] [10/11/12 Regression] '-fcompare-debug' failure (length) w/ -O2 -fnon-call-exceptions -fno-inline-small-functions since r10-3575-g629387a6586a7531
Date: Fri, 28 Jan 2022 09:50:31 +0000 [thread overview]
Message-ID: <bug-104263-4-FhqO5DeT5w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104263-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104263
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[10/11/12 Regression] |[10/11/12 Regression]
|'-fcompare-debug' failure |'-fcompare-debug' failure
|(length) w/ -O2 |(length) w/ -O2
|-fnon-call-exceptions |-fnon-call-exceptions
|-fno-inline-small-functions |-fno-inline-small-functions
| |since
| |r10-3575-g629387a6586a7531
CC| |ebotcazou at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r10-3575-g629387a6586a7531.
next prev parent reply other threads:[~2022-01-28 9:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 2:51 [Bug debug/104263] New: [10/11/12 Regression] '-fcompare-debug' failure (length) w/ -O2 -fnon-call-exceptions -fno-inline-small-functions asolokha at gmx dot com
2022-01-28 8:16 ` [Bug debug/104263] " rguenth at gcc dot gnu.org
2022-01-28 8:22 ` [Bug tree-optimization/104263] " rguenth at gcc dot gnu.org
2022-01-28 9:33 ` jakub at gcc dot gnu.org
2022-01-28 9:50 ` marxin at gcc dot gnu.org [this message]
2022-01-28 9:54 ` [Bug tree-optimization/104263] [10/11/12 Regression] '-fcompare-debug' failure (length) w/ -O2 -fnon-call-exceptions -fno-inline-small-functions since r10-3575-g629387a6586a7531 rguenth at gcc dot gnu.org
2022-01-28 9:54 ` rguenth at gcc dot gnu.org
2022-01-28 10:37 ` jakub at gcc dot gnu.org
2022-01-28 10:48 ` ebotcazou at gcc dot gnu.org
2022-01-28 12:30 ` cvs-commit at gcc dot gnu.org
2022-01-28 18:03 ` cvs-commit at gcc dot gnu.org
2022-01-28 18:05 ` [Bug tree-optimization/104263] [10/11 " jakub at gcc dot gnu.org
2022-02-19 8:02 ` cvs-commit at gcc dot gnu.org
2022-02-19 8:07 ` [Bug tree-optimization/104263] [10 " jakub at gcc dot gnu.org
2022-02-25 1:20 ` cvs-commit at gcc dot gnu.org
2022-05-10 8:23 ` cvs-commit at gcc dot gnu.org
2022-05-10 10:19 ` 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-104263-4-FhqO5DeT5w@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).