From: John Hendry <jj_hendry@bigpond.com>
To: gcc-help@gcc.gnu.org
Subject: Patch for gcc-10.3.0
Date: Mon, 12 Apr 2021 21:16:08 +1000 [thread overview]
Message-ID: <20210412211608.0406b3c6421ab9996318d5e6@bigpond.com> (raw)
Dear gcc maintainers,
I'm trying to install gcc-10.3.0 on a 64-bit PC running Crux Linux 3.5. Make gives the error "bit_AVX512VPTINTERSECT not declared" in cpuinfo.c, line 392 or so, and then AVX512BF16 is not declared 4 lines later.
The same thing was happening with 10.2 and I don't know whether I've misconfigured something to do with 32-bit libraries for cross-compiling or whether these bits refer to features of machines more advanced. Can I switch off support for these technological advances? I couldn't see anything in help for ../configure.
The closest thing I could find on the internet was on a gentoo forum but had no acknowledgement of a problem. The patches I've seen seem to be directed to Intel developers, at least not to ordinary users trying to compile gcc.
Can you confirm that it needs a patch or suggest some files I might modify?
Thank you for considering my case,
John Hendry
next reply other threads:[~2021-04-12 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 11:16 John Hendry [this message]
2021-04-12 12:29 ` Jonathan Wakely
2021-04-12 20:29 ` Jim Wilson
2021-04-12 20:34 ` Jonathan Wakely
2021-04-13 19:33 ` Jim Wilson
2021-04-13 19:50 ` Jonathan Wakely
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=20210412211608.0406b3c6421ab9996318d5e6@bigpond.com \
--to=jj_hendry@bigpond.com \
--cc=gcc-help@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).