public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/102509] [12 regression] new test case gcc.c-torture/compile/attr-complex-method.c is unresolved after r12-3901
Date: Tue, 28 Sep 2021 06:12:26 +0000 [thread overview]
Message-ID: <bug-102509-4-4qHySbJGLR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102509-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102509
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |marxin at gcc dot gnu.org,
| |tschwinge at gcc dot gnu.org
Ever confirmed|0 |1
Last reconfirmed| |2021-09-28
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to seurer from comment #0)
> UNRESOLVED: gcc.c-torture/compile/attr-complex-method.c -O2 -flto
> -fuse-linker-plugin -fno-fat-lto-objects scan-tree-dump-not optimized
> "__divdc3"
This variant only.
Likewise for the same variant of
'gcc.c-torture/compile/attr-complex-method-2.c'.
next prev parent reply other threads:[~2021-09-28 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 23:24 [Bug testsuite/102509] New: " seurer at gcc dot gnu.org
2021-09-28 6:12 ` tschwinge at gcc dot gnu.org [this message]
2021-09-28 8:37 ` [Bug testsuite/102509] " rguenth at gcc dot gnu.org
2021-09-30 9:56 ` marxin at gcc dot gnu.org
2021-09-30 12:17 ` cvs-commit at gcc dot gnu.org
2021-09-30 12:18 ` marxin 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-102509-4-4qHySbJGLR@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).