public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97247] Typos in <enqcmdintrin.h> Date: Tue, 29 Sep 2020 19:06:40 +0000 [thread overview] Message-ID: <bug-97247-4-EJqiB8SpAV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97247-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97247 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>: https://gcc.gnu.org/g:dec881f85abbddc6e37630b6e61ce621cea6acd7 commit r11-3531-gdec881f85abbddc6e37630b6e61ce621cea6acd7 Author: H.J. Lu <hjl.tools@gmail.com> Date: Tue Sep 29 11:40:46 2020 -0700 x86: Replace <enqcmdntrin.h> with <enqcmdintrin.h> Fix 2 typos in config/i386/enqcmdintrin.h by replacing <enqcmdntrin.h> with <enqcmdintrin.h>: [hjl@gnu-cfl-2 x86-gcc]$ echo "#include <enqcmdintrin.h>" | gcc -S -o /dev/null -x c - In file included from <stdin>:1: /usr/lib/gcc/x86_64-redhat-linux/10/include/enqcmdintrin.h:25:3: error: #error "Never use <enqcmdntrin.h> directly; include <x86intrin.h> instead." 25 | # error "Never use <enqcmdntrin.h> directly; include <x86intrin.h> instead." | ^~~~~ [hjl@gnu-cfl-2 x86-gcc]$ and _ENQCMDINTRIN_H_INCLUDED with _ENQCMDINTRIN_H_INCLUDED. gcc/ PR target/97247 * config/i386/enqcmdintrin.h: Replace <enqcmdntrin.h> with <enqcmdintrin.h>. Replace _ENQCMDNTRIN_H_INCLUDED with _ENQCMDINTRIN_H_INCLUDED.
next prev parent reply other threads:[~2020-09-29 19:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-29 18:25 [Bug target/97247] New: Typo " hjl.tools at gmail dot com 2020-09-29 18:47 ` [Bug target/97247] " hjl.tools at gmail dot com 2020-09-29 19:00 ` [Bug target/97247] Typos " hjl.tools at gmail dot com 2020-09-29 19:01 ` hjl.tools at gmail dot com 2020-09-29 19:06 ` cvs-commit at gcc dot gnu.org [this message] 2020-09-29 19:12 ` cvs-commit at gcc dot gnu.org 2020-09-29 19:12 ` 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-97247-4-EJqiB8SpAV@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: linkBe 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).