public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wwwhhhyyy333 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97231] New: Missing FSF copyright notes for some x86 intrinsic headers
Date: Mon, 28 Sep 2020 15:30:46 +0000	[thread overview]
Message-ID: <bug-97231-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97231

            Bug ID: 97231
           Summary: Missing FSF copyright notes for some x86 intrinsic
                    headers
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: wwwhhhyyy333 at gmail dot com
  Target Milestone: ---

Many x86 intrinsic header files doesn't have FSF copyright:

amxbf16intrin.h
amxint8intrin.h
amxtileintrin.h
avx512vp2intersectintrin.h
avx512vp2intersectvlintrin.h
pconfigintrin.h
tsxldtrkintrin.h
wbnoinvdintrin.h

             reply	other threads:[~2020-09-28 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 15:30 wwwhhhyyy333 at gmail dot com [this message]
2020-09-28 15:35 ` [Bug target/97231] " wwwhhhyyy333 at gmail dot com
2020-09-28 15:57 ` hjl.tools at gmail dot com
2020-09-29 12:41 ` cvs-commit at gcc dot gnu.org
2020-09-29 12:43 ` hjl.tools at gmail dot com
2020-09-29 18:08 ` cvs-commit at gcc dot gnu.org
2020-09-29 18:16 ` cvs-commit at gcc dot gnu.org
2020-09-29 18:20 ` cvs-commit at gcc dot gnu.org
2020-09-29 18:21 ` 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-97231-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).