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 c++/27397] [4.2 regression] ICE on invalid template argument
Date: Mon, 03 May 2021 12:01:45 +0000 [thread overview]
Message-ID: <bug-27397-4-xUkCvZMv4x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-27397-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27397
--- Comment #8 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:fd7eb4bc94cafa745eba75c64fa483a1689a5aad
commit r12-380-gfd7eb4bc94cafa745eba75c64fa483a1689a5aad
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Fri Feb 12 16:30:23 2021 -0800
GCC_CET_HOST_FLAGS: Check if host supports multi-byte NOPs
Sync with binutils for PR binutils/27397. Check if host supports
multi-byte NOPs before enabling CET on host.
config/
PR bootstrap/99703
* cet.m4 (GCC_CET_HOST_FLAGS): Check if host supports multi-byte
NOPs.
libiberty/
PR bootstrap/99703
* configure: Regenerated.
next parent reply other threads:[~2021-05-03 12:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-27397-4@http.gcc.gnu.org/bugzilla/>
2021-05-03 12:01 ` cvs-commit at gcc dot gnu.org [this message]
2006-05-02 19:21 [Bug c++/27397] New: " reichelt at gcc dot gnu dot org
2006-05-02 21:04 ` [Bug c++/27397] " pinskia at gcc dot gnu dot org
2006-05-03 16:00 ` bangerth at dealii dot org
2006-05-04 15:21 ` pinskia at gcc dot gnu dot org
2006-06-04 18:45 ` mmitchel at gcc dot gnu dot org
2006-07-05 18:29 ` jason at gcc dot gnu dot org
2006-07-06 0:57 ` reichelt at gcc dot gnu dot org
2006-07-17 3:22 ` mmitchel at gcc dot gnu dot org
2006-08-12 21:31 ` janis at gcc dot gnu dot org
2006-08-30 20:52 ` lmillward at gcc dot gnu dot org
2006-09-02 14:16 ` lmillward at gcc dot gnu dot org
2006-09-02 14:17 ` lmillward at gcc dot gnu dot 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-27397-4-xUkCvZMv4x@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).