public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95259] New: Duplicated codes in libgcc, driver-i386.c and i386-builtins.c
Date: Thu, 21 May 2020 12:55:35 +0000 [thread overview]
Message-ID: <bug-95259-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95259
Bug ID: 95259
Summary: Duplicated codes in libgcc, driver-i386.c and
i386-builtins.c
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: ubizjak at gmail dot com
Depends on: 95258, 91695, 95212, 95220
Target Milestone: ---
Target: i386, x86-64
There are duplicated codes in libgcc, driver-i386.c and i386-builtins.c.
It is very hard to keep them in sync and up to date. libgcc doesn't enable
any AVX512 ISAs if AVX512 isn't usable. But driver-i386.c only does it for
some AVX512 ISAs. libgcc only supports a subset of ISAs.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91695
[Bug 91695] [X86] get_available_features only sets FEATURE_GFNI and
FEATURE_VPCLMULQDQ when avx512_usable is true
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95212
[Bug 95212] enum processor_features is out of sync
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95220
[Bug 95220] Incorrect GFNI dectection
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95258
[Bug 95258] -march=native doesn't handle -mavx512vpopcntdq
next reply other threads:[~2020-05-21 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 12:55 hjl.tools at gmail dot com [this message]
2020-05-21 13:25 ` [Bug target/95259] " hjl.tools at gmail dot com
2020-05-21 13:25 ` hjl.tools at gmail dot com
2020-05-21 14:54 ` hjl.tools at gmail dot com
2020-05-24 11:36 ` hjl.tools at gmail dot com
2020-05-28 20:41 ` hjl.tools at gmail dot com
2020-06-24 12:50 ` cvs-commit at gcc dot gnu.org
2020-06-24 13:17 ` hjl.tools at gmail dot com
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-95259-4@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).