public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105157] [12 Regression] compile-time regressions with generic tuning since r12-7756-g27d8748df59fe6
Date: Wed, 06 Apr 2022 11:21:04 +0000 [thread overview]
Message-ID: <bug-105157-4-V8ujz2N1mg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105157-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105157
--- Comment #7 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #6)
> More to the point the cited rev. doesn't look like it should change anything
> for -mtune=generic. Maybe the "generic" config is always the last one on
> aarch64 and now "demeter"? At least there doesn't seem to be explicit
> "generic" configs like on x86_64.
We do have an explicit generic tuning struct, the ones with generic_* in the
name e.g. generic_tunings, but as you say, this patch doesn't change it at all.
we'll take a look.
next prev parent reply other threads:[~2022-04-06 11:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 9:50 [Bug target/105157] New: [12 Regression] compile-time regressions with generic tuning rguenth at gcc dot gnu.org
2022-04-05 9:53 ` [Bug target/105157] " rguenth at gcc dot gnu.org
2022-04-06 8:35 ` marxin at gcc dot gnu.org
2022-04-06 10:57 ` [Bug target/105157] [12 Regression] compile-time regressions with generic tuning since r12-7756-g27d8748df59fe6 marxin at gcc dot gnu.org
2022-04-06 10:57 ` marxin at gcc dot gnu.org
2022-04-06 11:05 ` marxin at gcc dot gnu.org
2022-04-06 11:13 ` rguenth at gcc dot gnu.org
2022-04-06 11:21 ` tnfchris at gcc dot gnu.org [this message]
2022-04-06 11:29 ` rguenth at gcc dot gnu.org
2022-04-06 17:24 ` avieira at gcc dot gnu.org
2022-04-08 14:15 ` cvs-commit at gcc dot gnu.org
2022-04-08 14:16 ` avieira 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-105157-4-V8ujz2N1mg@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).